Clippy lints / Correctness
Clippy lint · Correctness · checked with Clippy 0.1.99
clippy::infinite_iter: infinite iteration detected
What it meansChecks for iteration that is guaranteed to be infinite. It is in the correctness group and denied by default (the build fails).
What you see
error: infinite iteration detected --> main.rs:5:1 | 5 | iter::repeat(1_u8).collect::<Vec<_>>(); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#infinite_iter = note: `#[deny(clippy::infinite_iter)]` 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?
While there may be places where this is acceptable (e.g., in event streams), in most cases this is simply an error.
Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
use std::iter;
iter::repeat(1_u8).collect::<Vec<_>>();
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::infinite_iter)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
infinite_iter = "allow"One run
cargo clippy -- -A clippy::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 is guaranteed to 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.
Example
use std::iter;
iter::repeat(1_u8).collect::<Vec<_>>();
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- impl_hash_borrow_with_str_and_bytesthe semantics of `Borrow<T>` around `Hash` can't be satisfied when both `Borrow<str>` and `Borrow<[u8]>` are implemented
- impossible_comparisonsChecks for double comparisons that can never succeed
- ineffective_bit_maskChecks for bit masks in comparisons which can be removed without changing the outcome
- inherent_to_string_shadow_displaytype `main::A` implements inherent method `to_string(&self) -> String` which shadows the implementation of `Display`
- inline_fn_without_bodyuse of `#[inline]` on trait method `name` which has no body
- invalid_regexChecks regex creation (with Regex::new, RegexBuilder::new, or RegexSet::new) for correct regex syntax
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::impl_hash_borrow_with_str_and_bytesthe semantics of `Borrow<T>` around `Hash` can't be satisfied when both `Borrow<str>` and `Borrow<[u8]>` are implementedRead it next →Did this answer your question?