Email me

Clippy lints / Complexity

Clippy lint · Complexity · checked with Clippy 0.1.99

clippy::needless_splitn: unnecessary use of `splitn`

What it meansChecks for usage of str::splitn (or str::rsplitn) where using str::split would be the same. It is in the complexity group and warns by default.

What you see

warning: unnecessary use of `splitn`
 --> main.rs:4:9
  |
4 | let _ = str.splitn(3, '=').next().unwrap();
  |         ^^^^^^^^^^^^^^^^^^ help: try: `str.split('=')`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#needless_splitn
  = note: `#[warn(clippy::needless_splitn)]` 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 function split is simpler and there is no performance difference in these cases, considering that both functions return a lazy iterator.

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

let str = "key=value=add";
let _ = str.splitn(3, '=').next().unwrap();

Write this instead

let str = "key=value=add";
let _ = str.split('=').next().unwrap();

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
needless_splitn = "allow"

One run

cargo clippy -- -A clippy::needless-splitn

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
1.59.0added in Rust

Clippy's own documentation

What it does

Checks for usage of str::splitn (or str::rsplitn) where using str::split would be the same.

Why is this bad?

The function split is simpler and there is no performance difference in these cases, considering that both functions return a lazy iterator.

Example

let str = "key=value=add";
let _ = str.splitn(3, '=').next().unwrap();

Use instead:

let str = "key=value=add";
let _ = str.split('=').next().unwrap();

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

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?

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