Fix for corner case where RwLock
could be acquired in write mode while write locked
#300
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.
This PR contains a minor 2 line fix for a corner case where a
RwLock
could erroneously be acquired in write mode while already being write locked. This led to a panic sayingloom::RwLock state corrupt: "WouldBlock"
, while it instead should return theWouldBlock
error state onRwLock::try_write
or (potentially) signal a deadlock when callingRwLock::write
. I also took the liberty of adding some more test cases forRwLock
, which will also detect any regressions of this bug.