diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2025-02-27 08:56:39 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-27 08:56:39 +0100 |
| commit | 25db95ec4ab545e5e9569661a97a0940daa9b9ca (patch) | |
| tree | 78a2cce0a89c39a5c2d5b67e4f8727a3ccc4eb63 /library/std/src | |
| parent | 3499846073d44c99d2d67987804303b1e8fa0383 (diff) | |
| parent | 864cca80b02e9daa2c41440f1bf9787083c9f149 (diff) | |
| download | rust-25db95ec4ab545e5e9569661a97a0940daa9b9ca.tar.gz rust-25db95ec4ab545e5e9569661a97a0940daa9b9ca.zip | |
Rollup merge of #137455 - compiler-errors:drop-lint-dtor, r=oli-obk
Reuse machinery from `tail_expr_drop_order` for `if_let_rescope` Namely, it defines its own `extract_component_with_significant_dtor` which is a bit more accurate than `Ty::has_significant_drop`, since it has a hard-coded list of types from the ecosystem which are opted out of the lint.[^a] Also, since we extract the dtors themselves, adopt the same *label* we use in `tail_expr_drop_order` to point out the destructor impl. This makes it much clear what's actually being dropped, so it should be clearer to know when it's a false positive. This conflicts with #137444, but I will rebase whichever lands first. [^a]: Side-note, it's kinda a shame that now there are two functions that presumably do the same thing. But this isn't my circus, nor are these my monkeys.
Diffstat (limited to 'library/std/src')
0 files changed, 0 insertions, 0 deletions
