Clippy lint · Restriction · checked with Clippy 0.1.99

clippy::shadow_same: Checks for bindings that shadow other bindings already in scope, while just changing reference level or mutability

What it meansChecks for bindings that shadow other bindings already in scope, while just changing reference level or mutability. It is in the restriction group and off by default.

Does it matter?

To require that what are formally distinct variables be given distinct names. See also shadow_reuse and shadow_unrelated for other restrictions on shadowing.

Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.

How to fix it

Clippy does not fix this one automatically. Change the code by hand:

Flagged

let x = &x;

Write this instead

let y = &x; // use different variable name

Turn it off, or on

It is off by default. To use it, set it to warn or deny:

Whole crate (Cargo.toml)

[lints.clippy]
shadow_same = "warn"

In code

#![warn(clippy::shadow_same)]

One run

cargo clippy -- -W clippy::shadow-same

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.

Restrictiongroup

allowdefault level

nofixed by cargo clippy --fix

pre 1.29.0added in Rust

Clippy's own documentation

What it does

Checks for bindings that shadow other bindings already in scope, while just changing reference level or mutability.

Why restrict this?

To require that what are formally distinct variables be given distinct names.

See also shadow_reuse and shadow_unrelated for other restrictions on shadowing.

Example

let x = &x;

Use instead:

let y = &x; // use different variable name

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

Up next

Also worth your time

Did this answer your question?