Clippy lints / Style
Clippy lint · Style · checked with Clippy 0.1.99
clippy::just_underscores_and_digits: consider choosing a more descriptive name
What it meansChecks if you have variables whose name consists of just underscores and digits. It is in the style group and warns by default.
What you see
warning: consider choosing a more descriptive name --> main.rs:3:5 | 3 | let _1 = 1; | ^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#just_underscores_and_digits = note: `#[warn(clippy::just_underscores_and_digits)]` 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?
It’s hard to memorize what a variable means without a descriptive name.
Code that works but is not idiomatic Rust. Warns by default.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
let _1 = 1;
let ___1 = 1;
let __1___2 = 11;
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::just_underscores_and_digits)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
just_underscores_and_digits = "allow"One run
cargo clippy -- -A clippy::just-underscores-and-digitsThe [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 if you have variables whose name consists of just underscores and digits.
Why is this bad?
It’s hard to memorize what a variable means without a descriptive name.
Example
let _1 = 1;
let ___1 = 1;
let __1___2 = 11;
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- needless_returnunneeded `return` statement
- new_without_defaultChecks for public types with a pub fn new() -> Self method and no implementation of Default
- len_zeroChecks for getting the length of something via .len() just to compare to zero, and suggests using .is_empty() where applicable
- iter_nthcalled `.iter().nth()` on a `Vec`
- iter_nth_zeroChecks for the use of iter.nth(0)
- iter_skip_nextcalled `skip(..).next()` on an iterator
- legacy_numeric_constantsusage of a legacy numeric constant
- len_without_is_emptyChecks for items that implement .len() but not .is_empty()
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::needless_returnunneeded `return` statementRead it next →Did this answer your question?