diff options
| author | bors <bors@rust-lang.org> | 2022-11-22 17:21:23 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-11-22 17:21:23 +0000 |
| commit | 5595d7f5d5168477172dd2c2a958d445eed61422 (patch) | |
| tree | dc1b363a56b4ecb77505e74d677be0e6b1a36ecb /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 94ce4465e5746bd3ef4d60a16c5aba1e8f0a5b80 (diff) | |
| parent | ed183ee9acbc8b0c13a7a1a4859db9b4e7ca7d37 (diff) | |
| download | rust-5595d7f5d5168477172dd2c2a958d445eed61422.tar.gz rust-5595d7f5d5168477172dd2c2a958d445eed61422.zip | |
Auto merge of #9750 - kraktus:lazy_eval, r=xFrednet
Fix [`unnecessary_lazy_eval`] when type has significant drop fix for https://github.com/rust-lang/rust-clippy/issues/9427#issuecomment-1295742590 However current implementation gives too many false positive, rending the lint almost useless. I don't know what's the best way to check if a type has a "significant" drop (in the common meaning, not the internal rustc one, for example Option<(u8, u8)> should not be considered significant) changelog: Fix [`unnecessary_lazy_eval`] when type has significant drop
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions