The RW Lock mechanism accepts you get concurrent shared access to your data without waiting.
And get unique access with locks like a Mutex.
| RwLock | The RW Lock mechanism accepts you get concurrent shared access to your data without waiting.
And get unique access with locks like a Mutex.
|
| RwLockReadGuard | The Simple Write Lock Guard
As long as you have this guard, you have shared 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.
|
| RwLockReadGuardFuture | |
| RwLockReadOwnedGuard | An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an Arc. It is identical to WriteLockGuard, except that rather than borrowing the RWLock, it clones the Arc, incrementing the reference count. This means that unlike WriteLockGuard, it will have the 'static lifetime.
As long as you have this guard, you have shared access to the underlying T. The guard internally keeps a reference-couned pointer to the original RWLock, 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.
|
| RwLockReadOwnedGuardFuture | |
| RwLockWriteGuard | 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.
|
| RwLockWriteGuardFuture | |
| RwLockWriteOwnedGuard | An owned handle to a held RWLock.
This guard is only available from a RWLock that is wrapped in an Arc. It is identical to WriteLockGuard, except that rather than borrowing the RWLock, it clones the Arc, incrementing the reference count. This means that unlike WriteLockGuard, it will have the 'static lifetime.
As long as you have this guard, you have exclusive access to the underlying T. The guard internally keeps a reference-couned pointer to the original RWLock, 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.
|
| RwLockWriteOwnedGuardFuture | |