Email me

Clippy lints / Complexity

Clippy lint · Complexity · checked with Clippy 0.1.99

clippy::filter_next: Checks for usage of _.filter(_).next()

What it meansChecks for usage of _.filter(_).next(). It is in the complexity group and warns by default.

Does it matter?

Readability, this can be written more concisely as _.find(_).

Code that does something simple in a complicated way. Warns by default.

How to fix it

Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.

Flagged

vec.iter().filter(|x| **x == 0).next();

Write this instead

vec.iter().find(|x| **x == 0);

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::filter_next)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
filter_next = "allow"

One run

cargo clippy -- -A clippy::filter-next

The [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.

Complexitygroup
warndefault level
yesfixed by cargo clippy --fix
pre 1.29.0added in Rust

Up next

Related lintclippy::too_many_argumentsChecks for functions with too many parametersRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ