async-lock
async-lock copied to clipboard
A question about poisoning
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?
I wasn't around when the library was designed, but I think that not having poisoning makes the library simpler overall.
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.