-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Add RwLockReadGuard::map for transforming guards to contain sub-borrows. #30834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an interesting aliasing situation where there are two valid
&mut
pointers to the same data (although one of them just isn't used). In the past we've received PRs to avoid this sort of situation, although I believe there is no technical reason currently why this would cause problems. I guess though that we can't reborrow for the outer lifetime, that's considered as moving out of the mutex guard?This is when destructuring the mutex guard would be nice...
cc @gankro, @bluss
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'm out of the aliasing model game. LLVM is so broken I don't even know what to believe anymore... and Rust doesn't even vaguely have something to point to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed this when refactoring to store an
&mut T
directly; you can't just reborrow since that marks the reference returned by thecb
as borrowing the mutex, so you can't read out the lock/guard later.Since the
&mut
inthis.__data
is not used while the other exists, I figured we would be in the clear, but it is a bit of a sketchy situation.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note we actually don't really want to destructure the guard since we want panics in the
cb
to poison the mutex.