Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::no_effect: statement with no effect
What it meansChecks for statements which have no effect. It is in the complexity group and warns by default.
What you see
warning: statement with no effect --> main.rs:3:1 | 3 | 0; | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#no_effect = note: `#[warn(clippy::no_effect)]` on by default
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?
Unlike dead code, these statements are actually executed. However, as they have no effect, all they do is make the code less readable.
Code that does something simple in a complicated way. Warns by default.
How to fix it
Clippy does not fix this one automatically (its suggestion may change behaviour, so it only shows it). Change the code by hand:
Flagged
0;
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::no_effect)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
no_effect = "allow"One run
cargo clippy -- -A clippy::no-effectThe [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 statements which have no effect.
Why is this bad?
Unlike dead code, these statements are actually executed. However, as they have no effect, all they do is make the code less readable.
Example
0;
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_argumentsChecks for functions with too many parameters
- clone_on_copyusing `clone` on type `u64` which implements the `Copy` trait
- type_complexityChecks for types used in structs, parameters and let declarations above a certain complexity threshold
- needless_splitnunnecessary use of `splitn`
- needless_updateChecks for needlessly including a base struct on update when all fields are changed anyway. This lint is not applied to structs marked with non_exhaustive
- neg_cmp_op_on_partial_ordthe use of negated comparison operators on partially ordered types produces code that is hard to read and refactor, please consider using the `partial_cmp` method instead, to make it clear that the two values could be incomparable
- nonnull_unchecked_on_box_ptruse of `NonNull::new_unchecked` with `Box::into_raw`
- only_used_in_recursionparameter is only used in recursion
- option_as_ref_derefChecks for usage of _.as_ref().map(Deref::deref) or its aliases (such as String::as_str)
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_argumentsChecks for functions with too many parametersRead it next →Did this answer your question?