Yup - got given some Go at my previous work and I was immediately seeing potential data races when reviewing code. The type system definitely doesn't do much to help you there, nor does the runtime shield you. 
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
this was super helpful, "You can think of the borrow checker as a validator for a locking system: immutable references are shared read locks and mutable references are exclusive write locks. Under this mental model, accessing data via two independent write locks is not safe"
-
Indeed. It is a great analogy, but unfortunately I didn't come up with it ;-) See link in the text for the original quote.
- 1 more reply
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.
"Once you have experienced the benefits it [the borrow checker] brings, you’ll grow increasingly paranoid of potential bugs in code written in other languages. (I cannot longer think of sandboxfs’s Go implementation as robust.)"