Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::let_underscore_must_use: non-binding `let` on an expression with `#[must_use]` type
What it meansChecks for let _ = <expr> where expr is #[must_use] It is in the restriction group and off by default.
What you see
warning: non-binding `let` on an expression with `#[must_use]` type --> main.rs:7:1 | 7 | let _ = f(); | ^^^^^^^^^^^^ | = help: consider explicitly using expression value note: type is `std::result::Result` --> main.rs:7:9 | 7 | let _ = f(); | ^^^ = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#let_underscore_must_use = note: requested on the command line with `-W clippy::let-underscore-must-use`
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?
To ensure that all #[must_use] types are used rather than ignored.
Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
fn f() -> Result<u32, u32> {
Ok(0)
}
let _ = f();
// is_ok() is marked #[must_use]
let _ = f().is_ok();
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]
let_underscore_must_use = "warn"In code
#![warn(clippy::let_underscore_must_use)]One run
cargo clippy -- -W clippy::let-underscore-must-useThe [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 let _ = <expr> where expr is #[must_use]
Why restrict this?
To ensure that all #[must_use] types are used rather than ignored.
Example
fn f() -> Result<u32, u32> {
Ok(0)
}
let _ = f();
// is_ok() is marked #[must_use]
let _ = f().is_ok();
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- integer_division_remainder_useduse of `/` has been disallowed in this context
- iter_over_hash_typeiteration over unordered hash-based type
- large_include_fileChecks for the inclusion of large files via include_bytes!() or include_str!()
- let_underscore_untypednon-binding `let` without a type annotation
- little_endian_bytesuse of `to_le_bytes`
- lossy_float_literalliteral cannot be represented as the underlying type without loss of precision
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?