Add timed lock support to RWLock #5866
Merged
+48
−6
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 introduces timeout-based locking support for the
RWLock
type inSwoole\\Lock
, aligning its behavior withMutex
based.Changes introduced:
lock_read()
→lock_read(?float $timeout = null)
: Enables acquiring a read lock with an optional timeout.lockwait(float $timeout)
: Extended to supportRWLock
in addition toMutex
.These PHP-level API changes introduce new semantics around lock acquisition timing and may warrant further discussion regarding coroutine compatibility and expected behavior.