Mutex(3)

hii bestie πŸ’– welcome to Mutex(3), straight outta the OCaml library manual. We're talking locks for mutual exclusion, and yes she's iconic. πŸŽ€

✨ NAME ✨

Mutex β€” Locks for mutual exclusion.

🧩 Module 🧩

Module Mutex

πŸ“– Documentation πŸ“–

Module Mutex
 : sig end

okay so Mutexes (mutual-exclusion locks) are used to implement critical sections and protect shared mutable data structures against concurrent accesses. The typical use is β€” if m is the mutex associated with the data structure D β€” literally this:

Mutex.lock m;
(* Critical section that operates over D *);
Mutex.unlock m

πŸ” the actual API, bestie

  • type t β€” The type of mutexes.
  • val create : unit -> t β€” Return a new mutex. Fresh mutex just dropped ✨
  • val lock : t -> unit β€” Lock the given mutex. Only one thread can have the mutex locked at any time. A thread that attempts to lock a mutex already locked by another thread will suspend until the other thread unlocks the mutex.
Before4.12: Sys_error was not raised for recursive locking (platform-dependent behaviour).

Raises Sys_error if the mutex is already locked by the thread calling Mutex.lock.

  • val try_lock : t -> bool β€” Same as Mutex.lock, but does not suspend the calling thread if the mutex is already locked: just return false immediately in that case. If the mutex is unlocked, lock it and return true. No waiting, no drama πŸ’…
  • val unlock : t -> unit β€” Unlock the given mutex. Other threads suspended trying to lock the mutex will restart. The mutex must have been previously locked by the thread that calls Mutex.unlock.
Before4.12: Sys_error was not raised when unlocking an unlocked mutex or when unlocking a mutex from a different thread.

Raises Sys_error if the mutex is unlocked or was locked by another thread.

  • val protect : t -> (unit -> 'a) -> 'a β€” protect mutex f runs f() in a critical section where mutex is locked (using Mutex.lock); it then takes care of releasing mutex, whether f() returned a value or raised an exception.

The unlocking operation is guaranteed to always take place, even in the event an asynchronous exception (e.g. Sys.Break) is raised in some signal handler. That's the safety net, bestie 🫢

Since 5.1


big kiss and a sparkle πŸ’– this was OCamldoc, dated 2026-06-22, for Mutex(3) β€” periodt. πŸ‘‘

πŸ“¦ where this page comes from