Go Error Propagation and API Contracts.
I’ve been thinking about errors in Go quite a bit lately and what has been bothering me about the practice of error design and usage in the community. The critique starts with this code:
1 2 3 if err != nil { return err } It’s such a common piece of code that it has become a trope thanks to folks feeling like the apparent verbosity is an affront to their humanity.

Read in full here:

This thread was posted by one of our members via one of our news source trackers.