The author argues that mutex poisoning by default in Rust is a poor design choice for most applications, claiming it hurts performance, reduces readability, and encourages bad code patterns to work around its quirks. The post explains how poisoning detects when a mutex is unlocked while holding a poisoned guard after a panic, but suggests this solves a niche problem at significant cost.
Background
Mutex poisoning is a Rust feature where a Mutex returns an error if a thread panics while holding the lock, signaling that the protected data may be in an inconsistent state. This has been a long-standing debate topic in the Rust community regarding its usefulness versus overhead.
- Source
- Lobsters
- Published
- Nov 19, 2026 at 09:01 PM
- Score
- 5.0 / 10