a8d1258ba7
Add a config option `inherent-impl-lint-scope` to the lint `multiple_inherent_impl` to target a different scope according to people's needs. It can take three values: `module`, `file`, and `crate` (default). - `module` is the weakest option. It lints if there are two or more impls in the same module. - `file` is a bit stronger, since it lints if there are two or more impls in the same file. So, this triggers the lint (where it did not with module): - `crate` is the strongest of them; it triggers as soon as there are two or more impls anywhere in the crate. It is the current behaviour of the lint, so it's the default option. changelog: [`multiple_inherent_impl`] : Add config option (`module`, `file` or `crate`) to target specific scope fixes rust-lang/rust-clippy#14867 |
||
|---|---|---|
| .. | ||
| test_utils | ||
| ui | ||
| ui-cargo | ||
| ui-internal | ||
| ui-toml | ||
| workspace_test | ||
| check-fmt.rs | ||
| clippy.toml | ||
| compile-test.rs | ||
| config-consistency.rs | ||
| config-metadata.rs | ||
| dogfood.rs | ||
| integration.rs | ||
| lint_message_convention.rs | ||
| missing-test-files.rs | ||
| no-profile-in-cargo-toml.rs | ||
| symbols-used.rs | ||
| versioncheck.rs | ||
| workspace.rs | ||