Mutex poisoning is not for everyone
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
The author argues that Rust's default of mutex poisoning is a mistake for most applications. Poisoning adds a flag to every mutex, inflates generated code with panic-handling paths, and forces unwrap-style boilerplate, all to guard a niche case where a panic leaves a critical section half-finished.