Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::default_instead_of_iter_empty: `std::iter::empty()` is the more idiomatic way

What it meansIt checks for std::iter::Empty::default() and suggests replacing it with std::iter::empty(). It is in the style group and warns by default.

What you see

warning: `std::iter::empty()` is the more idiomatic way
 --> main.rs:3:9
  |
3 | let _ = std::iter::Empty::<usize>::default();
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `std::iter::empty::<usize>()`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#default_instead_of_iter_empty
  = note: `#[warn(clippy::default_instead_of_iter_empty)]` 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?

std::iter::empty() is the more idiomatic way.

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

let _ = std::iter::Empty::<usize>::default();
let iter: std::iter::Empty<usize> = std::iter::Empty::default();

Write this instead

let _ = std::iter::empty::<usize>();
let iter: std::iter::Empty<usize> = std::iter::empty();

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
default_instead_of_iter_empty = "allow"

One run

cargo clippy -- -A clippy::default-instead-of-iter-empty

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.64.0added in Rust

Clippy's own documentation

What it does

It checks for std::iter::Empty::default() and suggests replacing it with std::iter::empty().

Why is this bad?

std::iter::empty() is the more idiomatic way.

Example

let _ = std::iter::Empty::<usize>::default();
let iter: std::iter::Empty<usize> = std::iter::Empty::default();

Use instead:

let _ = std::iter::empty::<usize>();
let iter: std::iter::Empty<usize> = std::iter::empty();

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::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