Or at the other end of the scale, the average Rust programmer doesn't care that their code could panic if numbers stop making sense, for example if I'm summing the number of employees who quality for a bonus scheme, the fact that this operation (which I think might reach hundreds but likely is only dozens) could panic if it exceeds u32::MAX isn't worth linting. But if you write jet engine firmware, you need to take such "this can't happen" cases more seriously so you can turn on a lint which forbids these naive operations.
Clippy really is a labour of love project, and it’s been great to work with these folk <3
I will try to pick up some issues in the coming weeks.
Clippy is a large collection of mostly unrelated lints, and more are always added. Understandably, they accumulate craft. I think stopping new lints for some time is a reasonable thing to do to keep a healthy codebase.
The compiler and clippy use the same “engine” to lint, but they are focused on different use cases, with clippy being more general development, whereas the linter in rustc is focused on language usage.
