News for hackers. Stuff that matters.
Re:Updating the Go Memory Model by ferdowsi on Monday July 12, 2021 @04:12PM (#27814515)
I believe the guidance addresses this.

> Programs that modify data being simultaneously accessed by multiple goroutines must serialize such access.

> To serialize access, protect the data with channel operations or other synchronization primitives such as those in the sync and sync/atomic packages.

Go gives us `sync.WaitGroup` and `errgroup.Group` as abstractions to manage concurrent operations. I always end up guiding developers towards using these unless they absolutely can't (like responding to OS signals requires interacting with channels).

Re:Updating the Go Memory Model by pkaye on Monday July 12, 2021 @05:47PM (#27815500)
For OS signals now they added NotifyContext() which uses context instead of channels.