diff options
| author | bors <bors@rust-lang.org> | 2024-01-27 17:44:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-01-27 17:44:24 +0000 |
| commit | 276ce3936bd7621f0cfda08fa070056dd6f43efb (patch) | |
| tree | 469fa464bcc7653701071fe7925d437b65f95754 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 18e1f25a9f503de065fbe5cbc328954e0ae112cd (diff) | |
| parent | bd6e9202b47ec68841d58b1574361e09c5d7775b (diff) | |
| download | rust-276ce3936bd7621f0cfda08fa070056dd6f43efb.tar.gz rust-276ce3936bd7621f0cfda08fa070056dd6f43efb.zip | |
Auto merge of #12083 - cocodery:fix/issue11932, r=Alexendoo
Fix/Issue11932: assert* in multi-condition after unrolling will cause lint `nonminimal_bool` emit warning fixes [Issue#11932](https://github.com/rust-lang/rust-clippy/issues/11932) After `assert`, `assert_eq`, `assert_ne`, etc, assert family marcos unrolling in multi-condition expressions, lint `nonminimal_bool` will recognize whole expression as a entirety, analyze each simple condition expr of them, and check whether can simplify them. But `assert` itself is a entirety to programmers, we don't need to lint on `assert`. This commit add check whether lint snippet contains `assert` when try to warning to an expression. changelog: [`nonminimal_bool`] add check for condition expression
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
