In my experience this just doesn't hold for errors originating from a library. Because a good library interface should mostly be a black box it makes it really

In my experience this just doesn't hold for errors originating from a library. Because a good library interface should mostly be a black box it makes it really hard to understand the underlying cause of an error from something like a networking library or a database library without logging everything. God help you if you have client code that must be able to return errors originating from a library or from the client code itself. Stacktraces are probably the single most useful tool in debugging any issue and their absence in Go is one of my only enduring gripes with the language.