Mutex poisoning is not for everyone
Summary
The author argues that Rust's mutex poisoning is overkill for most applications, citing performance penalties, reduced readability, and the temptation to write brittle code to handle poisoned locks. The post discusses how poisoning is implemented, compares with non-poisoning variants and unwrap-based patterns, and advocates stabilizing nonpoisoning mutexes in std. It also covers readability concerns, potential workarounds, and the broader implications for library design.