microsoft / microsoft/rust-guidelines
Explain in M-STATIC-VERIFICATION general motivation for custom lints we picked & expand
Open
easy-pr
issue
- Dominant language
- Rust
- Stars
- 200
- Forks
- 25
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Add a few more words that they make code look nicer, etc.
Also add `redundant_pub_crate = "allow"`.
TODO: Any statistics which lints are usually enable / suppressed in ecosystem? IIRC there was an experiment about that a few years ago, but can't find it anymore.
Contributor guide
Research direction
Start at the M-STATIC-VERIFICATION section and inspect the Rust lint configuration to find where custom lints are documented and where redundant_pub_crate can be allowed. Done means the motivation is expanded, the requested lint setting is added, and the statistics TODO is resolved or clearly scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100