Golang concurrency model based on goroutines and channels is not free from sharp edges.
This page intends both (1) to collect helpful guidelines for writing concurrent code in Go and (2) to bring up well known potential issues to attention.
C1. Some channel operations cause runtime panic:
C2. Do not close a channel from a receiver goroutine. Closing the channel from a receiver could make future sender goroutines to panic.
C3. If a channel has multiple senders, do not close the channel from a sender goroutine. Closing the channel from a sender could make future sender goroutine to panic.
Alternatively, coordinate senders so that only the last sender to leave closes the channel (for instance by using either atomic int or sync.WaitGroup)
Last one sender to leave, turns off the lights, which can be controlled by a atomic int.
C4. It is not required to close an unused channel. If no goroutine is left referencing the channel, it will be garbage collected.
Note that it is only necessary to close a channel if the receiver is looking for a close. Closing the channel is a control signal on the channel indicating that no more data follows.
C5. Channels work well when enclosed in a 'select'.
If you are ever using a channel outside of a select in production code, you are probably doing it wrong.
C6. If you need bidirectional communication between two goroutines, consider using two unidirectional channels. Thus both channel sides will be able to use the close idiom to signal termination.
C7. Beware: one sender goroutine risks blocking indefinitely when writing on a channel if there is no goroutine left receiving from it.
C8. When designing a goroutine which provides service through channels, and at some point a running goroutine is no longer needed, consider exactly how it will finish. Otherwise, unused goroutines may leak idly servicing an unattended channel.
C9. Keep Dave Cheney's Four Channel Axioms in mind:
C10. 'select' never selects a blocking case.
G1. Only one goroutine accessing a piece of data is good practice.
In particular, consider structuring your program so that only one goroutine at a time is ever responsible for a particular piece of data.
G2. runtime.Goexit() terminates the goroutine that calls it.