Email me

Clippy lints / Suspicious

Clippy lint · Suspicious · checked with Clippy 0.1.99

clippy::cast_enum_truncation: casting `main::E::X` to `u8` will truncate the value

What it meansChecks for casts from an enum type to an integral type that will definitely truncate the value. It is in the suspicious group and warns by default.

What you see

warning: casting `main::E::X` to `u8` will truncate the value
 --> main.rs:4:9
  |
4 | let _ = E::X as u8;
  |         ^^^^^^^^^^
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#cast_enum_truncation
  = note: `#[warn(clippy::cast_enum_truncation)]` 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?

The resulting integral value will not match the value of the variant it came from.

Code that is most likely wrong or useless. Warns by default.

How to fix it

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

Flagged

enum E { X = 256 };
let _ = E::X as u8;

Turn it off, or on

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

On one item

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

Whole crate (Cargo.toml)

[lints.clippy]
cast_enum_truncation = "allow"

One run

cargo clippy -- -A clippy::cast-enum-truncation

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.

Suspiciousgroup
warndefault level
nofixed by cargo clippy --fix
1.61.0added in Rust

Clippy's own documentation

What it does

Checks for casts from an enum type to an integral type that will definitely truncate the value.

Why is this bad?

The resulting integral value will not match the value of the variant it came from.

Example

enum E { X = 256 };
let _ = E::X as u8;

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::by_ref_peekable_peekcalling `.by_ref().peekable().peek()` will advance the underlying iterator and consume its first outputRead 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