On Sun, Aug 5, 2018 at 8:25 PM Marvin Stenger <marvin.stenge...@gmail.com> wrote:
> Well it does. Does what? Even, what does what? > For this this case of chan.go there are multiple reasons working together, why it is ok to sometimes use a lock, othertimes only atomic access or even plain access: Maybe I misunderstand something. Are we both talking about a code path protected by a locked mutex and thus executing in a single goroutine with no other goroutine concurrently accessing the data protected by the mutex, ie. in a way such that no two goroutines read _and_ write the same data within the protected path? (Concurrent reads, but only reads are ok.) -- -j -- 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.
