Related to the previous discussion that probably spawned the question, the mutex acts as a load and store barrier, so you don't need to worry about whether the temp[1] and temp[2] assignments are visible to remote processors. When the mutex is acquired, that's guaranteed to be globally visible. This is a property of mutexes in Go, not a property of mutexes in general.
So yes, the second because it's a shorter critical section. But it's also safe because the mutex is a memory barrier. --dho 2016-11-06 21:55 GMT-08:00 Tamás Gulácsi <tgulacs...@gmail.com>: > The second. The section in lock should be as short as possible. > > -- > 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. -- 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.
