Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::iter_next_slice: Checks for usage of iter().next() or iter_mut().next() on a Slice or an Array

What it meansChecks for usage of iter().next() or iter_mut().next() on a Slice or an Array It is in the style group and warns by default.

Does it matter?

These can be shortened into .first() or .first_mut()

Code that works but is not idiomatic Rust. 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

a[2..].iter().next();
b.iter().next();
c.iter_mut().next();

Write this instead

a.get(2);
b.first();
c.first_mut();

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
iter_next_slice = "allow"

One run

cargo clippy -- -A clippy::iter-next-slice

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.

Stylegroup
warndefault level
yesfixed by cargo clippy --fix
1.46.0added in Rust

Up next

Related lintclippy::needless_returnunneeded `return` statementRead 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