36
Mutex poisoning is not for everyone
(bertptrs.nl)
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Credits
I already told you, convenience, developer experience. Ergonomics basically. None of this is fixed by some code snippet, whether it's an extension trait or wrapper type. That just makes things worse. This has nothing to do with performance, as I already said.
Can you point the notable relevant inconvenience, bad developer experience, and poor ergonomics developers are suffering from?
Is it all caused by a
lock()method returning aResult?Anything else?
Yes? I think I am done with this conversation. If you don't think this is a problem, we just disagree. Just move on, you don't have to convince everyone else who's been discussing this problem for years that it isn't a problem.
I haven't seen anyone else concede the performance talking point (under different banners), but proceeding to make this out to be a big issue. This includes this thread's OP which literally starts on-topic arguments with:
This is what makes your positioning weird.
My replies here, starting with pointing out the lack of benchmarks of real-world use-cases, come from actually bothering to read OP, IN FULL.