The race detector in v1.10 considers unsynchronized reads and writes on the `int` and `bool` types to be races:
https://gist.github.com/slingamn/886ebeba32f04294028cf0a60a8cc8c0 Are these instances of the race detector being stricter than the memory model? On Monday, March 19, 2018 at 8:59:15 PM UTC-4, Ian Lance Taylor wrote: > > On Mon, Mar 19, 2018 at 5:46 AM, shivaram via golang-nuts > <golan...@googlegroups.com <javascript:>> wrote: > > > > 2. The property that word-sized values are not subject to > > interleaving/tearing is an implementation detail, rather than a > guarantee of > > the Go memory model? > > My impression is that that is guaranteed by the Go memory model. But > the runtime package is in some sense not subject to the Go memory > model, since it is responsible for implementing the Go memory model. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
