Upgrade lock_api to 0.4.0
#3
Merged
Conversation
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
added 2 commits
July 4, 2020 11:04
This upgrade introduces a new `is_locked` function to the `Mutex` and `RawMutex` types. The default implementation for `RawMutex` works but is less efficient, so a new implementation is added.
phil-opp
added a commit
that referenced
this pull request
Jul 6, 2020
|
Published as v0.2.0 |
ghost
deleted the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 upgrade introduces a new
is_lockedfunction to theMutexandRawMutextypes. The default implementation forRawMutexworks, but is less efficient, so a new implementation is added.Also,
unlockwas markedunsafeinRawMutexbecause it cannot safely be called unless the lock is already held. This implementation already made this assumption.