Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::precedence_bits: Checks for bit shifting operations combined with bit masking/combining operators and suggest using parentheses
What it meansChecks for bit shifting operations combined with bit masking/combining operators and suggest using parentheses. It is in the restriction group and off by default.
Does it matter?
Not everyone knows the precedence of those operators by heart, so expressions like these may trip others trying to reason about the code.
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.
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]
precedence_bits = "warn"In code
#![warn(clippy::precedence_bits)]One run
cargo clippy -- -W clippy::precedence-bitsThe [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 bit shifting operations combined with bit masking/combining operators and suggest using parentheses.
Why restrict this?
Not everyone knows the precedence of those operators by heart, so expressions like these may trip others trying to reason about the code.
Example
0x2345 & 0xF000 >> 12 equals 5, while (0x2345 & 0xF000) >> 12 equals 2
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
- pathbuf_init_then_pushChecks for calls to push immediately after creating a new PathBuf
- pattern_type_mismatchtype of pattern does not match the expression type
- pointer_formatpointer formatting detected
- print_stderruse of `eprintln!`
- print_stdoutuse of `println!`
- pub_useusing `pub use`
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?