Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A question about poisoning #53

Closed
A248 opened this issue Jul 25, 2023 · 2 comments
Closed

A question about poisoning #53

A248 opened this issue Jul 25, 2023 · 2 comments

Comments

@A248
Copy link

A248 commented Jul 25, 2023

I am simply curious regarding why the locks in this library don't implement lock poisoning like those in the standard library. I'm using RwLock whose read and write locking methods are entirely error-free. What was the reasoning behind this design decision?
@notgull
Copy link
Member

notgull commented Jul 25, 2023

I wasn't around when the library was designed, but I think that not having poisoning makes the library simpler overall.

@notgull
Copy link
Member

notgull commented Jun 1, 2024

I do not plan on adding poisoning to this library. It could probably be implemented in a higher-level library on top of this one.

@notgull notgull closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@notgull @A248