Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::semicolon_outside_block: Suggests moving the semicolon from a block’s final expression outside of the block
What it meansSuggests moving the semicolon from a block’s final expression outside of the block. It is in the restriction group and off by default.
Does it matter?
For consistency it’s best to have the semicolon inside/outside the block. Either way is fine and this lint suggests outside the block. Take a look at semicolon_inside_block for the other alternative.
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
unsafe { f(x); }
Write this instead
unsafe { f(x) };
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]
semicolon_outside_block = "warn"In code
#![warn(clippy::semicolon_outside_block)]One run
cargo clippy -- -W clippy::semicolon-outside-blockThe [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
semicolon-outside-block-ignore-multiline: Whether to lint only if it’s singleline.
Clippy's own documentation
What it does
Suggests moving the semicolon from a block’s final expression outside of the block.
Why restrict this?
For consistency it’s best to have the semicolon inside/outside the block. Either way is fine
and this lint suggests outside the block.
Take a look at semicolon_inside_block for the other alternative.
Example
unsafe { f(x); }
Use instead:
unsafe { f(x) };
Configuration
-
semicolon-outside-block-ignore-multiline: Whether to lint only if it’s singleline.(default:
false)
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
- same_name_methodmethod's name is the same as an existing method in a trait
- 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
- separated_literal_suffixinteger type suffix should not be separated by an underscore
- shadow_reuse`x` is shadowed
- shadow_sameChecks for bindings that shadow other bindings already in scope, while just changing reference level or mutability
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?