golang-patterns

To handle errors in Go with proper context, wrap errors using fmt.Errorf with %w, implement custom error types, and use sentinel patterns. This approach improves debuggability by preserving the original error chain while adding meaningful contextual information.

Structured concurrency in Go uses contexts and errgroup to manage goroutine lifecycles. It ensures safe cancellation by propagating context cancellation signals, preventing goroutine leaks, and coordinating parallel task execution effectively.

Use Go generics with type constraints to write reusable, type-safe code. Define small interfaces and leverage interface composition to decouple components, minimizing dependencies while maintaining strict type safety.

Best practices for HTTP middleware chaining in Go involve creating idiomatic request handlers that pass requests through a sequence of middleware functions. This simplifies processing pipelines by cleanly separating cross-cutting concerns like logging and authentication.

Yes, you need Go 1.18 or higher to use modern generics and concurrency patterns. Go 1.18 introduced type parameters and constraints, which are essential for the standard library generics and interface composition patterns used in this skill.

Apply Go code review patterns to existing projects when auditing for error-handling and concurrency consistency. Progressively adopt idiomatic templates during project bootstrapping or reviews to elevate code quality and maintainability.