I too consider that if err != nil a bit complicated to type. Most times, I wrap it away in a function like your Check0. I know that the major “framework” for command line applications (cobra) has a similar logic with its checkError function.

I don’t think it is a taboo, but it is possibly just worse code in many cases. Handling error values is usually something that should be done thoughtfully. Panic is nice but can easily be overused and should not make it out of a package.

I too wish there was a better way, but in the form of proper enums and result and option types. However, wrapping in functions is fine in some cases not taboo.

As an aside, you probably don’t need a static union type for your min and max functions. I assume you could use comparable.

I would call it a taboo because it diverges from the general best practice. That makes your code harder to read and understand for people less familiar with “your style”. Given that code is read much more often that it is written, you are optimizing on the wrong end.

There is! See “Errors are values” from the Go blog: go.dev/blog/errors-are-values

I would rename Check to Must which there is at least some precedent for.