We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 0e1d60e commit 476f593Copy full SHA for 476f593
lib/concurrent/atomic/reentrant_read_write_lock.rb
@@ -21,7 +21,9 @@ module Concurrent
21
# also acquire a read lock OR a write lock more than once. Only when the read (or
22
# write) lock is released as many times as it was acquired, will the thread
23
# actually let it go, allowing other threads which might have been waiting
24
- # to proceed.
+ # to proceed. Therefore the lock can be upgraded by first acquiring
25
+ # read lock and then write lock and that the lock can be downgraded by first
26
+ # having both read and write lock a releasing just the write lock.
27
#
28
# If both read and write locks are acquired by the same thread, it is not strictly
29
# necessary to release them in the same order they were acquired. In other words,
0 commit comments