Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::no_effect_underscore_binding: binding to `_` prefixed variable with no side-effect
What it meansChecks for binding to underscore prefixed variable without side-effects. It is in the pedantic group and off by default.
What you see
warning: binding to `_` prefixed variable with no side-effect --> main.rs:3:5 | 3 | let _i_serve_no_purpose = 1; | ^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#no_effect_underscore_binding = note: `-W clippy::no-effect-underscore-binding` implied by `-W clippy::pedantic`
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 bindings are actually executed. However, as they have no effect and shouldn’t be used further on, all they do is make the code less readable.
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
let _i_serve_no_purpose = 1;
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]
no_effect_underscore_binding = "warn"In code
#![warn(clippy::no_effect_underscore_binding)]One run
cargo clippy -- -W clippy::no-effect-underscore-bindingThe [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 binding to underscore prefixed variable without side-effects.
Why is this bad?
Unlike dead code, these bindings are actually executed. However, as they have no effect and shouldn’t be used further on, all they do is make the code less readable.
Example
let _i_serve_no_purpose = 1;
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
- needless_for_eachneedless use of `for_each`
- needless_pass_by_valuethis argument is passed by value, but not consumed in the function body
- needless_raw_string_hashesunnecessary hashes around raw string literal
- no_mangle_with_rust_abi`#[no_mangle]` set on a function with the default (`Rust`) ABI
- non_std_lazy_staticsLints when once_cell::sync::Lazy or lazy_static! are used to define a static variable, and suggests replacing such cases with std::sync::LazyLock instead. Note: This lint will not trigger in crate with no_std context, or with MSRV < 1.80.0
- nonminimal_boolChecks for boolean expressions that can be written more concisely
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?