clippy::lint_groups_priority: Checks for lint groups with the same priority as lints in the Cargo.toml [lints] table. This lint will be removed once cargo#12918 is resolved

#[allow(clippy::lint_groups_priority)]
fn my_function() { /* ... */ }

[lints.clippy]
lint_groups_priority = "allow"

cargo clippy -- -A clippy::lint-groups-priority

Clippy's own documentation

What it does

Checks for lint groups with the same priority as lints in the Cargo.toml [lints] table.

This lint will be removed once cargo#12918 is resolved.

Why is this bad?

The order of lints in the [lints] is ignored, to have a lint override a group the priority field needs to be used, otherwise the sort order is undefined.

Known problems

Does not check lints inherited using lints.workspace = true

Example

[lints.clippy]
pedantic = "warn"
similar_names = "allow"

Use instead:

[lints.clippy]
pedantic = { level = "warn", priority = -1 }
similar_names = "allow"

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

• iter_skip_zerousage of `.skip(0)`
• iterator_step_by_zero`Iterator::step_by(0)` will panic at runtime
• let_underscore_lockChecks for let _ = sync_lock
• match_str_case_mismatchChecks for match expressions modifying the case of a string with non-compliant arms
• mem_replace_with_uninitChecks for mem::replace(&mut _, mem::uninitialized()) and mem::replace(&mut _, mem::zeroed())
• min_maxChecks for expressions where std::cmp::min and max are used to clamp values, but switched so that the result is constant

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker