lock_api 0.4.12

Wrappers to create fully-featured Mutex and RwLock types. Compatible with no_std.

This library provides type-safe and fully-featured [Mutex] and [RwLock] types which wrap a simple raw mutex or rwlock type. This has several benefits: not only does it eliminate a large portion of the work in implementing custom lock types, it also allows users to write code which is generic with regards to different lock implementations.

Basic usage of this crate is very straightforward:

  1. Create a raw lock type. This should only contain the lock state, not any data protected by the lock.
  2. Implement the RawMutex trait for your custom lock type.
  3. Export your mutex as a type alias for lock_api::Mutex, and your mutex guard as a type alias for lock_api::MutexGuard. See the example below for details.

This process is similar for [RwLock]s, except that two guards need to be exported instead of one. (Or 3 guards if your type supports upgradable read locks, see extension traits below for details)


use lock_api::{RawMutex, Mutex, GuardSend};
use std::sync::atomic::{AtomicBool, Ordering};

// 1. Define our raw lock type
pub struct RawSpinlock(AtomicBool);

// 2. Implement RawMutex for this type
unsafe impl RawMutex for RawSpinlock {
const INIT: RawSpinlock = RawSpinlock(AtomicBool::new(false));

// A spinlock guard can be sent to another thread and unlocked there
type GuardMarker = GuardSend;

fn lock(&self) {
// Note: This isn't the best way of implementing a spinlock, but it
// suffices for the sake of this example.
while !self.try_lock() {}

fn try_lock(&self) -> bool {
.compare_exchange(false, true, Ordering::Acquire, Ordering::Relaxed)

unsafe fn unlock(&self) {
self.0.store(false, Ordering::Release);

// 3. Export the wrappers. This are the types that your users will actually use.
pub type Spinlock<T> = lock_api::Mutex<RawSpinlock, T>;
pub type SpinlockGuard<'a, T> = lock_api::MutexGuard<'a, RawSpinlock, T>;

Extension traits

In addition to basic locking & unlocking functionality, you have the option of exposing additional functionality in your lock types by implementing additional traits for it. Examples of extension features include:

  • Fair unlocking (RawMutexFair, RawRwLockFair)
  • Lock timeouts (RawMutexTimed, RawRwLockTimed)
  • Downgradable write locks (RawRwLockDowngradable)
  • Recursive read locks (RawRwLockRecursive)
  • Upgradable read locks (RawRwLockUpgrade)

The Mutex and RwLock wrappers will automatically expose this additional functionality if the raw lock type implements these extension traits.

Cargo features

This crate supports three cargo features:

  • owning_ref: Allows your lock types to be used with the owning_ref crate.
  • arc_lock: Enables locking from an Arc. This enables types such as ArcMutexGuard. Note that this requires the alloc crate to be present.