Clippy lints / Style
Clippy lint · Style · checked with Clippy 0.1.99
clippy::mixed_case_hex_literals: inconsistent casing in hexadecimal literal
What it meansWarns on hexadecimal literals with mixed-case letter digits. It is in the style group and warns by default.
What you see
warning: inconsistent casing in hexadecimal literal --> main.rs:3:1 | 3 | 0x1a9BAcD | ^^^^^^^^^ | = help: consider using `0x1a9bacd` or `0x1A9BACD` = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#mixed_case_hex_literals = note: `#[warn(clippy::mixed_case_hex_literals)]` 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?
It looks confusing.
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
0x1a9BAcD
Write this instead
0x1A9BACD
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::mixed_case_hex_literals)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
mixed_case_hex_literals = "allow"One run
cargo clippy -- -A clippy::mixed-case-hex-literalsThe [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
Warns on hexadecimal literals with mixed-case letter digits.
Why is this bad?
It looks confusing.
Example
0x1a9BAcD
Use instead:
0x1A9BACD
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- needless_returnunneeded `return` statement
- new_without_defaultChecks for public types with a pub fn new() -> Self method and no implementation of Default
- len_zeroChecks for getting the length of something via .len() just to compare to zero, and suggests using .is_empty() where applicable
- missing_enforced_import_renamesChecks for imports that do not rename the item as specified in the enforced-import-renames config option. Note: Even though this lint is warn-by-default, it will only trigger if import renames are defined in the clippy.toml file
- missing_safety_docChecks for the doc comments of publicly visible unsafe functions and warns if there is no # Safety section
- mixed_attributes_styleChecks for items that have the same kind of attributes with mixed styles (inner/outer)
- module_inceptionChecks for modules that have the same name as their parent module
- multiple_bound_locationsbound is defined in more than one place
- must_use_unitthis unit-returning function has a `#[must_use]` attribute
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?