Clippy lints / Nursery
Clippy lint · Nursery · checked with Clippy 0.1.99
clippy::suspicious_operation_groupings: this sequence of operators looks suspiciously like a bug
What it meansChecks for unlikely usages of binary operators that are almost certainly typos and/or copy/paste errors, given the other usages of binary operators nearby. It is in the nursery group and off by default.
What you see
warning: this sequence of operators looks suspiciously like a bug --> main.rs:14:9 | 14 | self.x == other.y && self.y == other.y && self.z == other.z | ^^^^^^^^^^^^^^^^^ help: did you mean: `self.x == other.x` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#suspicious_operation_groupings = note: `-W clippy::suspicious-operation-groupings` implied by `-W clippy::nursery`
Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.
Does it matter?
They are probably bugs and if they aren’t then they look like bugs and you should add a comment explaining why you are doing such an odd set of operations.
New lints still being finished. Off by default and may have false positives.
How to fix it
Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Flagged
struct Vec3 {
x: f64,
y: f64,
z: f64,
}
impl Eq for Vec3 {}
impl PartialEq for Vec3 {
fn eq(&self, other: &Self) -> bool {
// This should trigger the lint because `self.x` is compared to `other.y`
self.x == other.y && self.y == other.y && self.z == other.z
}
}
Write this instead
// same as above except:
impl PartialEq for Vec3 {
fn eq(&self, other: &Self) -> bool {
// Note we now compare other.x to self.x
self.x == other.x && self.y == other.y && self.z == other.z
}
}
Turn it off, or on
It is off by default. To use it, set it to warn or deny:
Whole crate (Cargo.toml)
[lints.clippy]
suspicious_operation_groupings = "warn"In code
#![warn(clippy::suspicious_operation_groupings)]One run
cargo clippy -- -W clippy::suspicious-operation-groupingsThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Clippy's own documentation
What it does
Checks for unlikely usages of binary operators that are almost certainly typos and/or copy/paste errors, given the other usages of binary operators nearby.
Why is this bad?
They are probably bugs and if they aren’t then they look like bugs and you should add a comment explaining why you are doing such an odd set of operations.
Known problems
There may be some false positives if you are trying to do something unusual that happens to look like a typo.
Example
struct Vec3 {
x: f64,
y: f64,
z: f64,
}
impl Eq for Vec3 {}
impl PartialEq for Vec3 {
fn eq(&self, other: &Self) -> bool {
// This should trigger the lint because `self.x` is compared to `other.y`
self.x == other.y && self.y == other.y && self.z == other.z
}
}
Use instead:
// same as above except:
impl PartialEq for Vec3 {
fn eq(&self, other: &Self) -> bool {
// Note we now compare other.x to self.x
self.x == other.x && self.y == other.y && self.z == other.z
}
}
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further use
- single_option_map`fn` that only maps over argument
- string_lit_as_bytesChecks for the as_bytes method called on string literals that contain only ASCII characters
- suboptimal_flopsexponent for bases 2 and e can be computed more accurately
- too_long_first_doc_paragraphChecks if the first paragraph in the documentation of items listed in the module page is too long
- trailing_empty_arraytrailing zero-sized array in a struct which is not marked with a `repr` attribute
- trait_duplication_in_boundsthis trait bound is already specified in the where clause
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further useRead it next →Did this answer your question?