about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorllogiq <bogusandre@gmail.com>2025-01-30 20:39:07 +0000
committerGitHub <noreply@github.com>2025-01-30 20:39:07 +0000
commit398a5c2db9d16ed29b322ad431f7b8f2fdf633cd (patch)
treec740bcd5dfb0e0abc966288243d7277e8e63b771 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parentf51e18de3057d211a96edb39a71a17ce18f0ebee (diff)
parent8db9ecfd74732f4227421fd9bbf3c7704f594cbe (diff)
downloadrust-398a5c2db9d16ed29b322ad431f7b8f2fdf633cd.tar.gz
rust-398a5c2db9d16ed29b322ad431f7b8f2fdf633cd.zip
New lint: `precedence_bits`, with recent additions to `precedence` (#14115)
Commit 25505302665a707bedee68ca1f3faf2a09f12c00 has extended the
`precedence` lint to include bitmasking and shift operations. The lint
is warn by default, and this generates many hits, especially in embedded
or system code, where it is very idiomatic to use expressions such as `1
<< 3 | 1 << 5` without parentheses.

This commit splits the recent addition into a new lint, which is put
into the "restriction" category, while the original one stays in
"complexity", because mixing bitmasking and arithmetic operations is
less typical.

Fix #14097

changelog: [`precedence_bits`]: new lint
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions