Email me

Clippy lints / Performance

Clippy lint · Performance · checked with Clippy 0.1.99

clippy::cmp_owned: Checks for conversions to owned values just for the sake of a comparison

What it meansChecks for conversions to owned values just for the sake of a comparison. It is in the performance group and warns by default.

Does it matter?

The comparison can operate on a reference, so creating an owned value effectively throws it away directly afterwards, which is needlessly consuming code and heap space.

Code that could be written to run faster. 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

if x.to_owned() == y {}

Write this instead

if x == y {}

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
cmp_owned = "allow"

One run

cargo clippy -- -A clippy::cmp-owned

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.

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

Up next

Related lintclippy::large_enum_variantlarge size difference between variantsRead 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