토론: Go error handling: wrapping with %w, errors.Is and errors.As

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

번역이 없어 원문을 표시합니다. 원문

The `%v`-to-hide-implementation-details rule is the wrong tool for the stated goal. `%v` does not only hide `sql.ErrNoRows` from callers; it severs the whole chain, so `errors.Is(err, context.Canceled)` and `errors.Is(err, context.DeadlineExceeded)` stop working at every layer above, and those are exactly the checks an HTTP handler or a retry loop needs to distinguish a client abort from a gateway timeout from a retryable failure. It also hides `net.Error` timeouts and any classification a transport provides. What the Go blog's own example points at is translation, not severing: the repository matches the driver errors that callers should reason about and returns its own vocabulary (`fmt.Errorf("find user %d: %w", id, ErrNotFound)` when the driver reported no rows), and wraps everything else with `%w` so that cancellation and timeout values stay reachable. Callers then depend on the repository's sentinels and types while the context errors pass through. `%v` is defensible only where the wrapped error is genuinely uninteresting to every caller, which is rarer than the bullet suggests, and never on a path that can carry a context error.

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

번역이 없어 원문을 표시합니다. 원문

Two tooling details that make the article's rules enforceable. `go vet` ships an `errorsas` analyzer that reports `errors.As` calls whose second argument is not a non-nil pointer to a type implementing `error` or to an interface type; the usual mistake is `errors.As(err, myErr)` instead of `errors.As(err, &myErr)`, and at run time that mistake panics rather than returning false. Its `printf` analyzer reports a `%w` verb in any function other than `fmt.Errorf` (and functions vet recognises as wrappers of it), because `%w` in `fmt.Printf` or `log.Printf` prints `%!w(...)` instead of wrapping; both analyzers are in the subset that `go test` runs automatically. Worth adding to the sentinel bullet: `errors.New` returns a distinct value on every call, so a sentinel must be a package-level variable created once; two `errors.New("not found")` calls do not compare equal, which is what makes `errors.Is` against a re-created value fail silently.