golang

Idiomatic Go error handling uses custom error types and error wrapping to provide context. You unwrap errors using `errors.Is` and `errors.As` to inspect causes and build robust backend services without losing original stack trace information.

Safe concurrency in Golang uses goroutines and channels managed by context propagation for cancellation. This approach prevents race conditions by safely coordinating concurrent request processing, such as implementing a worker pool for backend tasks.

Table-driven tests in Go use slice structs to define input cases and expected outputs, iterating through them to execute assertions. This testing strategy ensures comprehensive coverage for both standard functions and integration tests.

This guidance covers both backend services and CLI tools. It focuses on production-ready code, safe concurrency primitives, and robust error management applicable to any idiomatic Go application architecture.

Context propagation is needed to manage timeouts and cancellation signals across goroutines. It ensures safe concurrent programming by allowing parent functions to signal child operations to terminate, preventing resource leaks in backend services.