On: Why we switched from Python to Go

[catnaroek]

Is Go even memory-safe in the presence of data races? Don't get me wrong, “memory safety” isn't a hard requirement in my book, but “memory safety or a formal semantics” is.

[cdoxsey → catnaroek]

If you're curious, the behavior is well defined: golang.org/ref/mem

[catnaroek → cdoxsey]

My English reading comprehension is admittedly poor, but I don't see any portion of the text that automatically implies that unsynchronized reads and writes are atomic.