Expand description
The RW Lock mechanism accepts you get shared access to your data without locking. The Ordered RW Lock will be locking all reads, which starting after write and unlocking them only when write will realize. It may be slow down the reads speed, but decrease time to write on systems, where it is critical.
BUT RW Lock has some limitations. You should avoid acquiring the second reading before realizing first inside the one future. Because it can happen that between your readings a write from another thread will acquire the mutex, and you will get a deadlock.
Structsยง
- Ordered
RwLock - The Ordered RW Lock will be locking all reads, which starting after write and unlocking them only when write will realize. It may be slow down the reads speed, but decrease time to write on systems, where it is critical.
- Ordered
RwLock Read Guard - The Simple Write Lock Guard
As long as you have this guard, you have shared access to the underlying
T
. The guard internally borrows theRWLock
, so the mutex will not be dropped while a guard exists. The lock is automatically released and waked the next locker whenever the guard is dropped, at which point lock will succeed yet again. - Ordered
RwLock Read Guard Future - Ordered
RwLock Read Owned Guard - An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an
Arc
. It is identical toWriteLockGuard
, except that rather than borrowing theRWLock
, it clones theArc
, incrementing the reference count. This means that unlikeWriteLockGuard
, it will have the'static
lifetime. As long as you have this guard, you have shared access to the underlyingT
. The guard internally keeps a reference-couned pointer to the originalRWLock
, so even if the lock goes away, the guard remains valid. The lock is automatically released and waked the next locker whenever the guard is dropped, at which point lock will succeed yet again. - Ordered
RwLock Read Owned Guard Future - Ordered
RwLock Write Guard - The Simple Write Lock Guard
As long as you have this guard, you have exclusive access to the underlying
T
. The guard internally borrows the RWLock, so the mutex will not be dropped while a guard exists. The lock is automatically released and waked the next locker whenever the guard is dropped, at which point lock will succeed yet again. - Ordered
RwLock Write Guard Future - Ordered
RwLock Write Owned Guard - An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an
Arc
. It is identical toWriteLockGuard
, except that rather than borrowing theRWLock
, it clones theArc
, incrementing the reference count. This means that unlikeWriteLockGuard
, it will have the'static
lifetime. As long as you have this guard, you have exclusive access to the underlyingT
. The guard internally keeps a reference-couned pointer to the originalRWLock
, so even if the lock goes away, the guard remains valid. The lock is automatically released and waked the next locker whenever the guard is dropped, at which point lock will succeed yet again. - Ordered
RwLock Write Owned Guard Future