The first example in the "Channel communication" section, it says
The write to a happens before the send on c, which happens before the corresponding receive on c completes, which happens before the print. >From the description, I feel that "the write to a happens before the send on c" is not caused by "the send on c happens before the corresponding receive on c completes". And "the corresponding receive on c completes happens before the print" is also independent to "the send on c happens before the corresponding receive on c completes". So it looks channel read and write operations really act as a fance to avoid exchanging relative orders of statements before and after the fence. -- 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.
