2 ms·
It is hard to use because you can’t just access the shared state. You have to annoyingly lock it, handle the guard object, etc. Each one of those layers has pro
by adastra22 11mo ago
It is hard to use because you can’t just access the shared state. You have to annoyingly lock it, handle the guard object, etc. Each one of those layers has protocols.
- bryanlarsen 11mo agoOf course you have to lock a mutex. You'd have to do that no matter the language, right? And that's what I meant by verbose/ugly. Each of those steps is usually an if let / else error. None of those steps are hard, but you have to do them every time.
- adastra22 11mo agoOh, plenty of people access shared state without proper locks all the time. Even experienced developers.
- bryanlarsen 11mo agoHeh. You're pedantically correct, the best kind. I meant "have to" in terms of "for correct operation you must" not "the compiler forces you to" since the latter isn't a thing in some languages.