Re:Go 1.1 RC1 is out
by sanderjd on Wednesday May 01, 2013 @09:07PM
(#5641886)
Honest question: aren't the concurrency primitives in Go largely intended to make concurrent memory accesses like this an anti-pattern? If so, why are so many races cropping up that a detector tool is necessary/very useful?
[ Parent
| on HN ]
> Honest question: aren't the concurrency primitives in Go largely intended to make concurrent memory accesses like this an anti-pattern
Intended, yes. But that doesn't mean we also develop "cleanly&properly" at all times, in the real world. It's a great "backup" for when formerly-prototyping-now-production code is getting slightly out of hand over time.
To expand on this point:
The Go-documentation has a couple of great examples [1] that could easily happen in the real world (before the first coffee).