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 don't think performance is the bottleneck. The real reason to not use poisoning mutexes is convenience and developer experience. The standard library should take such considerations heavily into account. A rare use case such as poisoning being requried should not be the default for mutexes in the standard library.
What does that even mean?
The interface concerns are as trivial as it gets:
This is basically is the one thing that shouldn't consume any mind tokens when it comes to synchronization primitive choice.
I'm not really sure what you're trying to say here. Are you saying that this is not a problem and everyone should just add this LockExt trait to all their code bases that uses Mutexes? Or..?
Every non-trivial code-base already has a
utilsmodule (sometimes a whole crate even) containing, in part, extension traits (and sometimes macros) to make some usages of some types nicer, in a way that is specific to the codebase (even in this case, a codebase might want a debug or trace log message for example, alongside the panic).It's a part of the language for a reason. It provides full idiomacity. And this is not limited to (poisoned or otherwise) synchronization primitives.
Talking about a method returning a
Resultlike it's a big deal must be some sort of splitting-hairs maxxing.And btw, as it just happens, such traits actually already exist, in a crate that is well-known to the ecosystem.
Well I would say this is not at all specific to the codebase - as I said above, it applies to basically all code bases that use mutexes, since poisoning is so rarely relevant.
These two statements are kind of strange to me:
and
If this is such a small deal, then using an external dependency is a terrible solution. That's like the whole left-pad situation, a dependency to solve an extremely small problem, but something that affects many, many code bases. That's exactly the use case that the standard library should cover, exactly so that you don't need to use an external dependency for such a trivial thing!
And yea you could say "duh just write the extension trait in your utils module" but this is just not acknowledging the problem at all and just sidestepping it. That's not helping anyone.
I was talking about what a codebase would want a non-Result-returning
lock()to look like (the panic message, or forcing abort, extra logging, signal handling...etc).Poisoning (as a negative) is only relevant if we are pretending it matters for performance. And you already conceded that this is not a part of the conversation as far as you're concerned.
The "rarely relevant" (as in playing any operative role at all) is also pure conjecture, or if we want to be nicer, it's totally contextual and use-case dependant.
lock_apiprovides a generic interface so you can e.g. seamlessly swipe out primitives fromparking_lotwith primitives fromspin, you know, the whole point behind generic programming!This is in no way comparable with
leftpad. And I wasn't actually pointing to it as a solution (to the largely non-existing problem). I just wanted to point out that extension traits for synchronisation primitives already exist with wide usage in the ecosystem, since you seemed to not be aware.If you have an aversion to extension traits. Here is a trivial unit struct wrapper solution. You don't even need to change the
Mutextype name or thelock()method name in your code.What is the notable relevant problem. Can you state it plainly?
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.