Only because I had started out my explanation in a prior thought trying to use ’naked’ read and write atomic fences, and having exactly 3 (main, t0, t1) exposed all that needed to be exposed of the problem. Yes, if this scales, there will be more goroutines than 3.
> On Jan 13, 2021, at 9:58 PM, Robert Engels <reng...@ix.netcom.com> wrote: > > Why limit yourself to two? Use N routines and have each process every N in > the list. > >> On Jan 13, 2021, at 7:25 PM, Nikolay Dubina <nikolay.dubina....@gmail.com> >> wrote: >> >> WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer http://bsc.es/disclaimer -- 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/BCA5F4FD-B52A-49EC-82F2-EE8E658C84C5%40bsc.es.
