This is not necessarily due to races. You can have this exact situation occurring in single threaded code. I don't think any mention of race issues was made here.
On Sun, 2019-10-27 at 08:53 +0000, roger peppe wrote: > On Sun, 27 Oct 2019, 00:04 Gert, <gert.cuyk...@gmail.com> wrote: > > > I believe it's going to be to hard to write a go vet analyser that > > could > > warn to detect unintended state change on a array from two > > different > > pointers. > > > > Isn't that why we have the race detector? > > -- > > 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. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/golang-nuts/30ac16bc-bc70-40a6-bc79-f41e3536d144%40googlegroups.com > > < > > https://groups.google.com/d/msgid/golang-nuts/30ac16bc-bc70-40a6-bc79-f41e3536d144%40googlegroups.com?utm_medium=email&utm_source=footer > > > > > . > > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/fd35e7a25f8a7e0ba57b68ceaf9fc95cece08fa8.camel%40kortschak.io.
