pub type MappedWriteGuard<'a, T> = MappedRwLockWriteGuard<'a, RawRwLock, T>;
Expand description
An RAII write lock guard returned by RwLockWriteGuard::map
, which can point to a
subfield of the protected data.
The main difference between MappedRwLockWriteGuard
and RwLockWriteGuard
is that the
former doesn’t support temporarily unlocking and re-locking, since that
could introduce soundness issues if the locked object is modified by another
thread.
Aliased Type§
struct MappedWriteGuard<'a, T> { /* private fields */ }
Layout§
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.
Size: 16 bytes
Implementations
Source§impl<'a, R, T> MappedRwLockWriteGuard<'a, R, T>
impl<'a, R, T> MappedRwLockWriteGuard<'a, R, T>
Sourcepub fn map<U, F>(
s: MappedRwLockWriteGuard<'a, R, T>,
f: F,
) -> MappedRwLockWriteGuard<'a, R, U>
pub fn map<U, F>( s: MappedRwLockWriteGuard<'a, R, T>, f: F, ) -> MappedRwLockWriteGuard<'a, R, U>
Make a new MappedRwLockWriteGuard
for a component of the locked data.
This operation cannot fail as the MappedRwLockWriteGuard
passed
in already locked the data.
This is an associated function that needs to be
used as MappedRwLockWriteGuard::map(...)
. A method would interfere with methods of
the same name on the contents of the locked data.
Sourcepub fn try_map<U, F>(
s: MappedRwLockWriteGuard<'a, R, T>,
f: F,
) -> Result<MappedRwLockWriteGuard<'a, R, U>, MappedRwLockWriteGuard<'a, R, T>>
pub fn try_map<U, F>( s: MappedRwLockWriteGuard<'a, R, T>, f: F, ) -> Result<MappedRwLockWriteGuard<'a, R, U>, MappedRwLockWriteGuard<'a, R, T>>
Attempts to make a new MappedRwLockWriteGuard
for a component of the
locked data. The original guard is return if the closure returns None
.
This operation cannot fail as the MappedRwLockWriteGuard
passed
in already locked the data.
This is an associated function that needs to be
used as MappedRwLockWriteGuard::try_map(...)
. A method would interfere with methods of
the same name on the contents of the locked data.
Source§impl<'a, R, T> MappedRwLockWriteGuard<'a, R, T>where
R: RawRwLockFair + 'a,
T: 'a + ?Sized,
impl<'a, R, T> MappedRwLockWriteGuard<'a, R, T>where
R: RawRwLockFair + 'a,
T: 'a + ?Sized,
Sourcepub fn unlock_fair(s: MappedRwLockWriteGuard<'a, R, T>)
pub fn unlock_fair(s: MappedRwLockWriteGuard<'a, R, T>)
Unlocks the RwLock
using a fair unlock protocol.
By default, RwLock
is unfair and allow the current thread to re-lock
the RwLock
before another has the chance to acquire the lock, even if
that thread has been blocked on the RwLock
for a long time. This is
the default because it allows much higher throughput as it avoids
forcing a context switch on every RwLock
unlock. This can result in one
thread acquiring a RwLock
many more times than other threads.
However in some cases it can be beneficial to ensure fairness by forcing
the lock to pass on to a waiting thread if there is one. This is done by
using this method instead of dropping the MappedRwLockWriteGuard
normally.