diff options
| author | bors <bors@rust-lang.org> | 2023-12-08 13:39:47 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-12-08 13:39:47 +0000 |
| commit | 1c8cbe79abd1ee75cbbc0b4a93d873c7d1a5fd8f (patch) | |
| tree | 4366b92973feda6c04cea1635fe85e03fb556886 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 2793e8d103f7f977f8b672558c18f6ab1dc4a578 (diff) | |
| parent | 56d20c2b53db2c2d39ee3e8368c5cd556c35f5b0 (diff) | |
| download | rust-1c8cbe79abd1ee75cbbc0b4a93d873c7d1a5fd8f.tar.gz rust-1c8cbe79abd1ee75cbbc0b4a93d873c7d1a5fd8f.zip | |
Auto merge of #11907 - cocodery:issue11885, r=y21,xFrednet
Add a function to check whether binary oprands are nontrivial fixes [#issue11885](https://github.com/rust-lang/rust-clippy/issues/11885) It's hard to check whether operator is overrided through context of lint. So, assume non-trivial structure like tuple, array or sturt, using a overrided binary operator in this lint, which might cause a side effict. This is not detected before. Althrough this might weaken the ability of this lint, it may more useful than before. Maybe this lint will cause an error, but now, it not. And assuming side effect of non-trivial structure with operator is not a bad thing, right? changelog: Fix: [`no_effect`] check if binary operands are nontrivial
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions