Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::while_let_loop: this loop could be written as a `while let` loop
What it meansDetects loop + match combinations that are easier written as a while let loop. It is in the complexity group and warns by default.
What you see
warning: this loop could be written as a `while let` loop --> main.rs:4:1 | 4 | / loop { 5 | | let x = match y { 6 | | Some(x) => x, 7 | | None => break, ... | 10 | | } | |_^ help: try: `while let Some(x) = y { .. }` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#while_let_loop = note: `#[warn(clippy::while_let_loop)]` 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?
The while let loop is usually shorter and more 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
let y = Some(1);
loop {
let x = match y {
Some(x) => x,
None => break,
};
// ..
}
Write this instead
let y = Some(1);
while let Some(x) = y {
// ..
};
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::while_let_loop)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
while_let_loop = "allow"One run
cargo clippy -- -A clippy::while-let-loopThe [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
Detects loop + match combinations that are easier
written as a while let loop.
Why is this bad?
The while let loop is usually shorter and more
readable.
Example
let y = Some(1);
loop {
let x = match y {
Some(x) => x,
None => break,
};
// ..
}
Use instead:
let y = Some(1);
while let Some(x) = y {
// ..
};
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
- useless_nonzero_new_unchecked`NonZeroUsize::new()` and `Option::unwrap()` can be safely used in a `const` context
- useless_transmuteChecks for transmutes to the original type of the object and transmutes that could be a cast
- vec_box`Vec<T>` is already on the heap, the boxing is unnecessary
- wildcard_in_or_patternsChecks for wildcard pattern used with others patterns in same match arm
- zero_divided_by_zeroconstant division of `0.0` with `0.0` will always result in NaN
- zero_prefixed_literalthis is a decimal constant
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?