Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::same_functions_in_if_condition: Checks for consecutive ifs with the same function call
What it meansChecks for consecutive ifs with the same function call. It is in the pedantic group and off by default.
Does it matter?
This is probably a copy & paste error. Despite the fact that function can have side effects and if works as intended, such an approach is implicit and can be considered a “code smell”.
Stricter lints with some false positives. Off by default; opt in with clippy::pedantic.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
if foo() == bar {
…
} else if foo() == bar {
…
}
Write this instead
if foo() == bar {
…
} else if foo() == baz {
…
}
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]
same_functions_in_if_condition = "warn"In code
#![warn(clippy::same_functions_in_if_condition)]One run
cargo clippy -- -W clippy::same-functions-in-if-conditionThe [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 consecutive ifs with the same function call.
Why is this bad?
This is probably a copy & paste error.
Despite the fact that function can have side effects and if works as
intended, such an approach is implicit and can be considered a “code smell”.
Example
if foo() == bar {
…
} else if foo() == bar {
…
}
This probably should be:
if foo() == bar {
…
} else if foo() == baz {
…
}
or if the original code was not a typo and called function mutates a state,
consider move the mutation out of the if condition to avoid similarity to
a copy & paste error:
let first = foo();
if first == bar {
…
} else {
let second = foo();
if second == bar {
…
}
}
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_linesChecks for functions with a large amount of lines
- missing_errors_docChecks the doc comments of publicly visible functions that return a Result type and warns if there is no # Errors section
- must_use_candidateChecks for public functions that have no #[must_use] attribute, but return something not already marked must-use, have no mutable arg and mutate no statics
- ref_optionWarns when a function signature uses &Option<T> instead of Option<&T>
- ref_option_refsince `&` implements the `Copy` trait, `&Option<&T>` can be simplified to `Option<&T>`
- return_self_not_must_usemissing `#[must_use]` attribute on a method returning `Self`
- same_length_and_capacityChecks for usages of Vec::from_raw_parts and String::from_raw_parts where the same expression is used for the length and the capacity
- self_only_used_in_recursion`self` is only used in recursion
- semicolon_if_nothing_returnedconsider adding a `;` to the last statement for consistent formatting
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_linesChecks for functions with a large amount of linesRead it next →Did this answer your question?