36
you are viewing a single comment's thread
view the rest of the comments
[-] TehPers@beehaw.org 1 points 1 day ago* (last edited 1 day ago)

I'm confused by this. saa::Lock does support poisoning, but it appears to be manual. You need to both manually mark it as poisoned via lock.poison_lock() and manually check if it's poisoned with the return value from locking. You can easily ignore poisoning entirely - it's actually more opt-in rather than forced on you. So sure this supports poisoning, but it's not forced on you like std::sync::Mutex, and saa::Lock isn't anything close to a complete Mutex alternative anyway.

It seems to support lock_api apparently (presumably as the locking implementations behind it?), but lock_api::Mutex doesn't appear to support poisoning at all.

this post was submitted on 18 Nov 2026
36 points (100.0% liked)

Rust

8379 readers
30 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 3 years ago
MODERATORS