diff options
| author | bors <bors@rust-lang.org> | 2025-08-09 03:19:26 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-08-09 03:19:26 +0000 |
| commit | 2de2456fb7b2b55cb104bb03f30edd145c6015a3 (patch) | |
| tree | 0a7e1e293ad1b9e832d66bb9bcb2ebd6bab66d9d /compiler/rustc_parse/src | |
| parent | 4c7749e8c8e50ad146da599eea3a250160c1bc2b (diff) | |
| parent | 0bdaef5b63fe2d557483e72732e463b86ffb041b (diff) | |
| download | rust-2de2456fb7b2b55cb104bb03f30edd145c6015a3.tar.gz rust-2de2456fb7b2b55cb104bb03f30edd145c6015a3.zip | |
Auto merge of #143376 - dianne:guard-scope, r=matthewjasper
add a scope for `if let` guard temporaries and bindings This fixes my concern with `if let` guard drop order, namely that the guard's bindings and temporaries were being dropped after their arm's pattern's bindings, instead of before (https://github.com/rust-lang/rust/pull/141295#issuecomment-2968975596). The guard's bindings and temporaries now live in a new scope, which extends until (but not past) the end of the arm, guaranteeing they're dropped before the arm's pattern's bindings. This only introduces a new scope for match arms with guards. Perf results (https://github.com/rust-lang/rust/pull/143376#issuecomment-3034922617) seemed to indicate there wasn't a significant hit to introduce a new scope on all match arms, but guard patterns (rust-lang/rust#129967) will likely benefit from only adding new scopes when necessary (with some patterns requiring multiple nested scopes). Tracking issue for `if_let_guard`: rust-lang/rust#51114 Tests are adapted from examples by `@traviscross,` `@est31,` and myself on rust-lang/rust#141295.
Diffstat (limited to 'compiler/rustc_parse/src')
0 files changed, 0 insertions, 0 deletions
