Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::maybe_infinite_iter: Checks for iteration that may be infinite
What it meansChecks for iteration that may be infinite. It is in the pedantic group and off by default.
Does it matter?
While there may be places where this is acceptable (e.g., in event streams), in most cases this is simply an error.
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 infinite_iter = 0..;
[0..].iter().zip(infinite_iter.take_while(|x| *x > 5));
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]
maybe_infinite_iter = "warn"In code
#![warn(clippy::maybe_infinite_iter)]One run
cargo clippy -- -W clippy::maybe-infinite-iterThe [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 iteration that may be infinite.
Why is this bad?
While there may be places where this is acceptable (e.g., in event streams), in most cases this is simply an error.
Known problems
The code may have a condition to stop iteration, but this lint is not clever enough to analyze it.
Example
let infinite_iter = 0..;
[0..].iter().zip(infinite_iter.take_while(|x| *x > 5));
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
- 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
- match_wild_err_arm`Err(_)` matches all errors
- match_wildcard_for_single_variantsChecks for wildcard enum matches for a single variant
- mismatching_type_param_order`Foo` has a similarly named generic type parameter `B` in its declaration, but in a different order
- missing_fields_in_debugmanual `Debug` impl does not include all fields
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?