go-concurrency-review

To find goroutine leaks and race conditions in Go code, review goroutine lifecycle management, enforce explicit termination paths, and mandate running tests with the race detector. This process identifies unsafe concurrency patterns and missing context handling in long-running services.

Common unsafe Go concurrency patterns include improper channel closing, copying mutexes by value, and incorrect synchronization. A code review should validate minimal lock scopes, channel sizing, and signal channel conventions to prevent deadlocks and data races.

To ensure proper context propagation in Go concurrent systems, enforce context-first function parameters and verify cancellation handling. Checking these rules during code review prevents goroutine leaks and ensures long-running services respond to termination signals correctly.

You should use errgroup instead of raw goroutines when managing parallel work that requires coordinated error handling and explicit termination. Enforcing errgroup usage during design prevents goroutine leaks by ensuring all spawned goroutines exit cleanly when an error occurs.

To validate channel sizing and mutex placement in Go producer consumer pipelines, review channel conventions and ensure minimal lock scopes. This prevents deadlocks and incorrect synchronization by warning against copying mutexes by value and verifying proper channel closing.