One of my big takeaways from Erlang was to write small processes that communicate over channels. One of the reasons I got into Rust was that it initially looked like a lot of code would be written that way, but it didn't seem to take off.
-
-
-
A lot of code in Rust is written that way. Servo is, for example.
- 2 more replies
New conversation -
-
-
We could all use SeqCst everywhere but we don’t want to… for reasons.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That was just sloppy. Yes, atomics are hard, but releasing a lock with relaxed ordering? That's not a bug, that's negligence.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Honestly guidance has always been "Relaxed/Consume are for specialised situations" If it's locking it's Acquire/Release or stronger
-
(Consume is a really awkward one, basically impossible for a compiler to support but also what weakly ordered CPUs give you implicitly due to the fact that real things obey temporal causality)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.