Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::enum_variant_names: variant name ends with the enum's name

What it meansDetects enumeration variants that are prefixed or suffixed by the same characters. It is in the style group and warns by default.

What you see

warning: variant name ends with the enum's name
 --> main.rs:4:5
  |
4 |     BlackForestCake,
  |     ^^^^^^^^^^^^^^^
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#enum_variant_names
  = note: `#[warn(clippy::enum_variant_names)]` 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?

Enumeration variant names should specify their variant, not repeat the enumeration name.

Code that works but is not idiomatic Rust. Warns by default.

How to fix it

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

Flagged

enum Cake {
    BlackForestCake,
    HummingbirdCake,
    BattenbergCake,
}

Write this instead

enum Cake {
    BlackForest,
    Hummingbird,
    Battenberg,
}

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
enum_variant_names = "allow"

One run

cargo clippy -- -A clippy::enum-variant-names

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

  • avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.
  • enum-variant-name-threshold: The minimum number of enum variants for the lints about variant names to trigger
Stylegroup
warndefault level
nofixed by cargo clippy --fix
pre 1.29.0added in Rust

Clippy's own documentation

What it does

Detects enumeration variants that are prefixed or suffixed by the same characters.

Why is this bad?

Enumeration variant names should specify their variant, not repeat the enumeration name.

Limitations

Characters with no casing will be considered when comparing prefixes/suffixes This applies to numbers and non-ascii characters without casing e.g. Foo1 and Foo2 is considered to have different prefixes (the prefixes are Foo1 and Foo2 respectively), as also Bar螃, Bar蟹

Example

enum Cake {
    BlackForestCake,
    HummingbirdCake,
    BattenbergCake,
}

Use instead:

enum Cake {
    BlackForest,
    Hummingbird,
    Battenberg,
}

Configuration

  • avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.

    (default: true)

  • enum-variant-name-threshold: The minimum number of enum variants for the lints about variant names to trigger

    (default: 3)

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