-
### Describe your use case
We have lints for when a `struct` changes "kind":
- [`tuple_struct_to_plain_struct`](https://github.com/obi1kenobi/cargo-semver-checks/blob/main/src/lints/tuple_struc…
-
### Summary
`clippy::mutex_integer` lints on usages as well as definitions, which seems redundant (and could be unactionable if this happens cross-crate).
### Reproducer
I tried this code ([playgro…
-
There are more and more issues about managing lints in Clippy popping up. Lints
are hard to implement with a guarantee of no/few false positives (FPs). One way
to address this might be to introduce …
-
(Elaborating on https://github.com/rust-lang/rust/issues/66220#issuecomment-557537105)
I think that the current state of `improper_ctypes` is difficult to maintain and extend -- especially once we …
-
I think it's a good feature, but also not something we do for other linters (e.g. `no_tab_linter()` is the first that comes to mind as a linter that tends to hit on many lines in a row).
Do you thi…
-
It would be nice to have a way to make Clippy ignore all lints that were added starting with a certain Rust version.
This would be useful to minimize the chance of breaking the build in projects th…
ojeda updated
2 months ago
-
Such warnings tend to be false positives.
Examples where the lint is allowed:
- Build context: https://github.com/trailofbits/dylint/blob/4438f402591d05e369636f54e18b4bab232702b5/dylint/build.rs#L23
…
-
We can still decide that a function is clear enough from the name and supress it explicitly, but we want to be explicit about it.
-
### Description
Over at the `bevy_cli` project, we're implementing custom lints for Bevy, and bootstrapping off of Clippy's existing tools :) We'd love to publish this to crates.io so folks can `carg…
-
### Description
Clippy currently has an "Added in" field for lints, I think it'd be a good idea to introduce an "Updated In" field that has the version in which fixes / improvements / category chan…