This is not the issue I am referring to, I am referring to https://github.com/golang/go/issues/5045
-----Original Message----- >From: Marvin Renich <m...@renich.org> >Sent: Nov 12, 2019 11:30 AM >To: golang-nuts <golang-nuts@googlegroups.com> >Subject: Re: [go-nuts] What is the correct way to access/modify slice elements >concurrently > >[I almost missed this post because you did not reply to the thread.] > >* Robert Engels <reng...@ix.netcom.com> [191108 11:41]: >> See https://github.com/golang/go/issues/10958 for using atomics in >> tight/busy-wait loops. > >This doesn't have anything to do with atomics. Atomic operations are >just one of many, many things you can do in a busy loop. There is >nothing about atomics that is any more relevant to this issue than the >increment statement, i++. > >...Marvin > >-- >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/20191112173043.6mfa7iejihhkasos%40basil.wdw. -- 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/921647355.5105.1573581609714%40wamui-abby.atl.sa.earthlink.net.
