Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::many_single_char_names: 7 bindings with single-character names in scope
What it meansChecks for too many variables whose name consists of a single character. It is in the pedantic group and off by default.
What you see
warning: 7 bindings with single-character names in scope --> main.rs:3:6 | 3 | let (a, b, c, d, e, f, g) = (...); | ^ ^ ^ ^ ^ ^ ^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#many_single_char_names = note: `-W clippy::many-single-char-names` 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?
It’s hard to memorize what a variable means without a descriptive name.
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 (a, b, c, d, e, f, g) = (...);
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]
many_single_char_names = "warn"In code
#![warn(clippy::many_single_char_names)]One run
cargo clippy -- -W clippy::many-single-char-namesThe [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.
Settings in clippy.toml
single-char-binding-names-threshold: The maximum number of single char bindings a scope may have
Clippy's own documentation
What it does
Checks for too many variables whose name consists of a single character.
Why is this bad?
It’s hard to memorize what a variable means without a descriptive name.
Example
let (a, b, c, d, e, f, g) = (...);
Configuration
-
single-char-binding-names-threshold: The maximum number of single char bindings a scope may have(default:
4)
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
- manual_let_elseWarn of cases where let...else could be used
- manual_midpointChecks for manual implementation of midpoint
- manual_string_newempty String is being created manually
- map_unwrap_orChecks for usage of option.map(_).unwrap_or(_) or option.map(_).unwrap_or_else(_) or result.map(_).unwrap_or_else(_)
- match_boolChecks for matches where match expression is a bool
- match_same_armsChecks for match with identical arm bodies. Note: Does not lint on wildcards if the non_exhaustive_omitted_patterns_lint feature is enabled and disallowed
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?