pub struct Mutex<R, T: ?Sized> { /* private fields */ }
Expand description
A mutual exclusion primitive useful for protecting shared data
This mutex will block threads waiting for the lock to become available. The
mutex can also be statically initialized or created via a new
constructor. Each mutex has a type parameter which represents the data that
it is protecting. The data can only be accessed through the RAII guards
returned from lock
and try_lock
, which guarantees that the data is only
ever accessed when the mutex is locked.
Implementations
Creates a new mutex in an unlocked state ready for use.
Consumes this mutex, returning the underlying data.
Acquires a mutex, blocking the current thread until it is able to do so.
This function will block the local thread until it is available to acquire the mutex. Upon returning, the thread is the only thread with the mutex held. An RAII guard is returned to allow scoped unlock of the lock. When the guard goes out of scope, the mutex will be unlocked.
Attempts to lock a mutex in the thread which already holds the lock will result in a deadlock.
Attempts to acquire this lock.
If the lock could not be acquired at this time, then None
is returned.
Otherwise, an RAII guard is returned. The lock will be unlocked when the
guard is dropped.
This function does not block.
Returns a mutable reference to the underlying data.
Since this call borrows the Mutex
mutably, no actual locking needs to
take place—the mutable borrow statically guarantees no locks exist.
Forcibly unlocks the mutex.
This is useful when combined with mem::forget
to hold a lock without
the need to maintain a MutexGuard
object alive, for example when
dealing with FFI.
Safety
This method must only be called if the current thread logically owns a
MutexGuard
but that guard has be discarded using mem::forget
.
Behavior is undefined if a mutex is unlocked when not locked.
Returns the underlying raw mutex object.
Note that you will most likely need to import the RawMutex
trait from
lock_api
to be able to call functions on the raw mutex.
Safety
This method is unsafe because it allows unlocking a mutex while
still holding a reference to a MutexGuard
.
Returns a raw pointer to the underlying data.
This is useful when combined with mem::forget
to hold a lock without
the need to maintain a MutexGuard
object alive, for example when
dealing with FFI.
Safety
You must ensure that there are no data races when dereferencing the
returned pointer, for example if the current thread logically owns
a MutexGuard
but that guard has been discarded using mem::forget
.
Forcibly unlocks the mutex using a fair unlock procotol.
This is useful when combined with mem::forget
to hold a lock without
the need to maintain a MutexGuard
object alive, for example when
dealing with FFI.
Safety
This method must only be called if the current thread logically owns a
MutexGuard
but that guard has be discarded using mem::forget
.
Behavior is undefined if a mutex is unlocked when not locked.
Attempts to acquire this lock until a timeout is reached.
If the lock could not be acquired before the timeout expired, then
None
is returned. Otherwise, an RAII guard is returned. The lock will
be unlocked when the guard is dropped.
Attempts to acquire this lock until a timeout is reached.
If the lock could not be acquired before the timeout expired, then
None
is returned. Otherwise, an RAII guard is returned. The lock will
be unlocked when the guard is dropped.