Tags: omenar/guide
Tags
Add guidance on goroutine lifecycle management (uber-go#158) In general, we prefer for goroutines to have well-managed lifecycles. No uncontrolled background work that cannot be stopped. This change tries to distill some of the guidance around it into a style guide entry. In particular, - goroutines must end or be stoppable - APIs must block for goroutines to finish - `init()` should never spawn a goroutine