go-concurrency

This skill covers concurrency patterns and best practices from Google's Go Style Guide and Uber's Go Style Guide, including goroutine management, channel usage, mutex handling, and synchronization. Normative : When you spawn goroutines, make it clear when or whether they exit. Goroutines can leak by blocking on channel sends or receives. The garbage collector will not terminate a goroutine blocked on a channel even if no other goroutine has a reference to the channel. Even when goroutines do not leak, leaving them in-flight when no longer needed causes: Write concurrent code so goroutine lifetimes are evident. Keep synchronization-related code constrained within function scope and factor logic into synchronous functions. Every goroutine must have a predictable stop mechanism: Source : Uber Go Style Guide Use sync.WaitGroup for multiple goroutines: Use a done channel for a single goroutine: init() functions should not spawn goroutines. If a package needs a background goroutine, expose an object that manages the goroutine's lifetime with a method ( Close , Stop , Shutdown ) to stop and wait for it.