diff options
| author | Fridtjof Stoldt <xFrednet@gmail.com> | 2025-01-10 11:58:29 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-10 11:58:29 +0000 |
| commit | 5c2601af15c6cba486c5d00a28dc31d8915d26eb (patch) | |
| tree | 129c06d2b5619fcbf0b5ade7dddaa4511002797f /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 197d58d59171acd4a903f04ce1a4be7e299b3b46 (diff) | |
| parent | c686ffd193fc6c745caf8bb46f935e2ef17ee264 (diff) | |
| download | rust-5c2601af15c6cba486c5d00a28dc31d8915d26eb.tar.gz rust-5c2601af15c6cba486c5d00a28dc31d8915d26eb.zip | |
Do not propose to elide lifetimes if this causes an ambiguity (#13929)
Some lifetimes in function return types are not bound to concrete content and can be set arbitrarily. Clippy should not propose to replace them by the default `'_` lifetime if such a lifetime cannot be determined unambigously. I added a field to the `LifetimeChecker` and `Usage` to flag lifetimes that cannot be replaced by default ones, but it feels a bit hacky. Fix #13923 changelog: [`needless_lifetimes`]: remove false positives by checking that lifetimes can indeed be elided
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions