Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::separated_literal_suffix: integer type suffix should not be separated by an underscore
What it meansWarns if literal suffixes are separated by an underscore. To enforce separated literal suffix style, see the unseparated_literal_suffix lint. It is in the restriction group and off by default.
What you see
warning: integer type suffix should not be separated by an underscore --> main.rs:3:1 | 3 | 123832_i32 | ^^^^^^^^^^ help: remove the underscore: `123832i32` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#separated_literal_suffix = note: requested on the command line with `-W clippy::separated-literal-suffix`
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?
Suffix style should be consistent.
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 can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Flagged
123832_i32
Write this instead
123832i32
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]
separated_literal_suffix = "warn"In code
#![warn(clippy::separated_literal_suffix)]One run
cargo clippy -- -W clippy::separated-literal-suffixThe [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 if literal suffixes are separated by an underscore.
To enforce separated literal suffix style,
see the unseparated_literal_suffix lint.
Why restrict this?
Suffix style should be consistent.
Example
123832_i32
Use instead:
123832i32
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- self_named_module_filesChecks that module layout uses only mod.rs files
- semicolon_inside_blockSuggests moving the semicolon after a block to the inside of the block, after its last expression
- semicolon_outside_blockSuggests moving the semicolon from a block’s final expression outside of the block
- shadow_reuse`x` is shadowed
- shadow_sameChecks for bindings that shadow other bindings already in scope, while just changing reference level or mutability
- shadow_unrelatedChecks for bindings that shadow other bindings already in scope, either without an initialization or with one that does not even use the original value
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?