Mutex poisoning is not for everyone
6 comments · rust
- Comments5
6 comments · rust
Story details from Lobsters ↗ · linked article on bertptrs.nl.
Mutex poisoning is not for everyone was first seen on Lobsters · Hottest on Nov 19, 2026. Since then it has appeared in 30 checks on 2 different days. Its best position was #4 of 25, reached on Nov 20, 00:52 UTC. It is #4 right now, holding steady at #4 over the last 6 checks.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
▲ as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
I realize that rust is no longer a young language where change can rapidly happen, but it's a shame that people are so afraid to introduce edition breaking changes, this is what editions are for. The issues with poisoning mutexes are well documented, and I think it would be a shame to keep it as the default going…
Couldn't disagree harder with this post. It basically makes two claims: 1. Poisoning costs performance, both for bookkeeping and panic propagation 2. Uptime is more important than correctness For 1, yeah, but that's consistent with the rest of the standard library.…
code in later editions must work together with code in older editions. That would make these changes very challenging. Is it such a big deal to use another Mutex from a library?
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 20, 03:52 UTC it is #4, holding steady at #4 over the last 6 checks.
#4 on Lobsters · Hottest, on Nov 20, 00:52 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 19, 2026 and has been on the list on 2 days (30 checks) since.