rust-lang / rust-lang/rust-clippy
Production lint category
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
About
This lint category collects all production code related lints, currently only including todo, unimplemented, dbg_macro, print_stdout and use_debug. This allows people to easily check whether they should release their code without having to remember the names of multiple lints and have to add and remove them, and allows Clippy to add more similar lints and have them be automatically enabled for all Rust production builds. Having these lints being in the restriction category doesn't really make sense because they are very useful for all Rust projects, just not all the time.
Drawbacks
It is a whole new lint category for just a couple lints.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review how Clippy currently groups the todo, unimplemented, dbg_macro, print_stdout, and use_debug lints, then determine the design for a production lint category. Done means the category is defined for these lints and future similar lints can be enabled through it for production builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100