Fix UnwrapUnsafeBinder handling in borrow conflict detection #147796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Replace
todo!()
with proper conflict analysis forUnwrapUnsafeBinder
projection elements inplaces_conflict.rs
.UnwrapUnsafeBinder
is treated as a transparent wrapper that doesn't affect place aliasing, returningEqualOrDisjoint
when both projections match.Changes
place_projection_conflict()
to handleUnwrapUnsafeBinder
projections correctlyTesting
Test Results
Verification
The test correctly identifies borrow conflicts when the same place is borrowed mutably multiple times, demonstrating that
UnwrapUnsafeBinder
is properly handled as a transparent projection that preserves aliasing semantics.