Add re-entry support to synchronized #26
Merged
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.
If you have many methods that use
synchronized
on a single mutex, but they should be able to call each other, it becomes a mess without re-entry support.This does have the side effect of a slight behavior change in case a
Semaphore
instead of aMutex
is passed. While aMutex
simply didn't work before, aSemaphore
would have consumed two or more locks instead of just one now on nested calls.