Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::mem_replace_option_with_some: replacing an `Option` with `Some(..)`

What it meansChecks for mem::replace() on an Option with Some(…). It is in the style group and warns by default.

What you see

warning: replacing an `Option` with `Some(..)`
 --> main.rs:4:16
  |
4 | let replaced = std::mem::replace(&mut an_option, Some(1));
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `Option::replace()` instead: `an_option.replace(1)`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#mem_replace_option_with_some
  = note: `#[warn(clippy::mem_replace_option_with_some)]` 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?

Option already has the method replace() for taking its current value (Some(…) or None) and replacing it with Some(…).

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 mut an_option = Some(0);
let replaced = std::mem::replace(&mut an_option, Some(1));

Write this instead

let mut an_option = Some(0);
let taken = an_option.replace(1);

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
mem_replace_option_with_some = "allow"

One run

cargo clippy -- -A clippy::mem-replace-option-with-some

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.

Settings in clippy.toml

  • msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml
Stylegroup
warndefault level
yesfixed by cargo clippy --fix
1.87.0added in Rust

Clippy's own documentation

What it does

Checks for mem::replace() on an Option with Some(…).

Why is this bad?

Option already has the method replace() for taking its current value (Some(…) or None) and replacing it with Some(…).

Example

let mut an_option = Some(0);
let replaced = std::mem::replace(&mut an_option, Some(1));

Is better expressed with:

let mut an_option = Some(0);
let taken = an_option.replace(1);

Configuration

  • msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml

    (default: current version)

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