Clippy lints / Correctness
Clippy lint · Correctness · checked with Clippy 0.1.99
clippy::enum_clike_unportable_variant: C-like enum variant discriminant is not portable to 32-bit targets
What it meansChecks for C-like enumerations that are repr(isize/usize) and have values that don’t fit into an i32. It is in the correctness group and denied by default (the build fails).
What you see
error: C-like enum variant discriminant is not portable to 32-bit targets --> main.rs:5:5 | 5 | X = 0x1_0000_0000, | ^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#enum_clike_unportable_variant = note: `#[deny(clippy::enum_clike_unportable_variant)]` 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?
This will truncate the variant value on 32 bit architectures, but works fine on 64 bit.
Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
#[repr(usize)]
enum NonPortable {
X = 0x1_0000_0000,
Y = 0,
}
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_clike_unportable_variant)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
enum_clike_unportable_variant = "allow"One run
cargo clippy -- -A clippy::enum-clike-unportable-variantThe [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.
Clippy's own documentation
What it does
Checks for C-like enumerations that are
repr(isize/usize) and have values that don’t fit into an i32.
Why is this bad?
This will truncate the variant value on 32 bit architectures, but works fine on 64 bit.
Example
#[repr(usize)]
enum NonPortable {
X = 0x1_0000_0000,
Y = 0,
}
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- derive_ord_xor_partial_ordLints against manual PartialOrd and Ord implementations for types with a derived Ord or PartialOrd implementation
- derived_hash_with_manual_eqLints against manual PartialEq implementations for types with a derived Hash implementation
- eager_transmutethis transmute is always evaluated eagerly, even if the condition is false
- eq_opChecks for equal operands to comparison, logical and bitwise, difference and division binary operators (==, >, etc., &&, ||, &, |, ^, - and /)
- erasing_opthis operation will always return zero. This is likely not the intended outcome
- if_let_mutexChecks for Mutex::lock calls in if let expression with lock calls in any of the else blocks
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::derive_ord_xor_partial_ordLints against manual PartialOrd and Ord implementations for types with a derived Ord or PartialOrd implementationRead it next →Did this answer your question?