The bigger issue is that returning the error without wrapping provides zero context and after a crash you're stuck trying to figure out which of a hundred calls to Write was responsible for "write error" or some other equally ambiguous message that's nearly impossible to track down.
So you have to resort to a poor man's stack trace:
if err != nil {
return fmt.Errorf("my thing: %w", err)
}
(We use wrapcheck via golangci-lint to enforce it because not having context for an error has bitten us so many times)
So you have to resort to a poor man's stack trace: if err != nil { return fmt.Errorf("my thing: %w", err) }
(We use wrapcheck via golangci-lint to enforce it because not having context for an error has bitten us so many times)