News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by catnaroek on Tuesday October 17, 2017 @08:59PM (#15496180)
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.
Re:Why we switched from Python to Go by cdoxsey on Wednesday October 18, 2017 @05:58AM (#15497954)
If you're curious, the behavior is well defined: golang.org/ref/mem
Re:Why we switched from Python to Go by catnaroek on Wednesday October 18, 2017 @02:10PM (#15501454)
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.