Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::op_ref: Checks for arguments to == which have their address taken to satisfy a bound and suggests to dereference the other argument instead

What it meansChecks for arguments to == which have their address taken to satisfy a bound and suggests to dereference the other argument instead It is in the style group and warns by default.

Does it matter?

It is more idiomatic to dereference the other argument.

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

&x == y

Write this instead

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::op_ref)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
op_ref = "allow"

One run

cargo clippy -- -A clippy::op-ref

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
pre 1.29.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