I think it is simpler to create a SyncPoint with Wait and Release methods - it is easily implemented with a WaitGroup and a Semaphore.
> On Jan 16, 2021, at 9:31 PM, Pete Wilson <peter.wil...@bsc.es> wrote: > > By ‘at the same time’ I would understand that none of them are able to see > the counter in the wait group after one member had triggered release. > > That is, I believed that “release by any go routine (that is, a Wait() done > by any collaborating goroutine which saw a zero counter) " happened before > "any go routine did anything else beyond returning from Wait()” > > If that were the case, none of them would ever see a non-zero count after any > one of them had seen it, and so no race condition could exist > > You suggest that that is not the case. > > (I don’t intend to be obtuse, even if I seem so) > > — P > >> On Jan 16, 2021, at 8:38 PM, Robert Engels <reng...@ix.netcom.com> wrote: >> >> It does release them all at once. They all become ready to run at the “same >> time” - the scheduler has to get them to run. Even if the release was atomic >> it would make no difference in the race condition. >> >>>> On Jan 16, 2021, at 7:35 PM, Pete Wilson <peter.wil...@bsc.es> 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 > > > > > > > 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 -- 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/7FC7791B-8B33-4593-B995-A4F61368A62C%40ix.netcom.com.
