Best practice is to return concrete types for everything, but error is one of those "special" cases that people tend to return an `error` for, IME.
You can always unwrap it via type assertion, however ugly that may be.
Re:Griping about Go
by thegeekpirate on Thursday February 07, 2019 @06:31PM
(#19109753)
> But best practice is to return concrete types.
You're taking this as an absolute when you shouldn't be. There's plenty of places in the standard library that don't follow this "rule".
But best practice is to return concrete types.
Also, `err` is just an example in this minimal snippet. It can happen with any variable.
Here's a similar snippet: https://play.golang.org/p/WKPey_PL_ht -- Looks impossible to crash. :P
Spoiler: it's a boxed null, not a null.