Surelock
Shares rank 5 of 8 Rust crates by recommenders
A Rust mutex library that enforces a total lock ordering to prevent deadlocks, praised for clear, explicit design without macros. Critics note it doesn't detect locking the same mutex twice.
A Rust mutex library that enforces a total lock ordering to prevent deadlocks, praised for clear, explicit design without macros. Critics note it doesn't detect locking the same mutex twice.
8 people gave an opinion
- recommend it
- 6
- criticize it
- 2
- approval share
- 75%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Rigorous lock ordering prevents deadlocks
“It's great to see more 'DB-style' rigour (like total ordering for locks) making its way into library design.”
Comment from 11 Apr 2026 in “Surelock: Deadlock-Free Mutexes for Rust” “That's pretty awesome. Dead locks are extremely tough to debug.”
Comment from 11 Apr 2026 in “Surelock: Deadlock-Free Mutexes for Rust” Well-designed, well-written library
“the second restriction seems to me to be fundamental to the design”
Comment from 11 Apr 2026 in “Surelock: Deadlock-Free Mutexes for Rust” “This is a well written article about a well written library.”
Comment from 12 Apr 2026 in “Surelock: Deadlock-Free Mutexes for Rust”
Other Rust crates people recommend
The four most recommended other Rust crates, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| anyhow (Rust crate) | 34 | 10 | 77% | 5 | — | Approved |
| Rayon | 18 | 2 | 90% | 10 | — | Approved |
| thiserror | 16 | 8 | 67% | 5 | — | Approved |
| rand crate | 9 | 3 | 75% | 4 | — | — |
| SurelockThis page | 6 | 2 | 75% | 1 | — | — |
What people said
All 8 comments that mention it, newest first. Each links to the original comment.
“This is a well written article about a well written library.”
“Forcing the user to assign in a level means that it's clear(er?) to users what's happening, we don't need fancy (and difficult to debug) macro magic”
“That feels like a lot of new cognitive burden.”
“the second restriction seems to me to be fundamental to the design”
“the fact that it doesn't detect locking the same mutex twice makes no sense”
“It's great to see more 'DB-style' rigour (like total ordering for locks) making its way into library design.”
“That's pretty awesome. Dead locks are extremely tough to debug.”
“an incremental improvement on Fuschia's tree_lock, with the sharp edges sanded off”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.