Show HN: Error return traces for Go, inspired by Zig

The logo is awesome. Has an artist been hired to create it?

I read the README but I'm not understanding yet why the return path might be what you want. The stack trace at error creation sounds more useful.

While from a first instance, this package seems a bit overkill, I think the idea is interesting and is something that can be improved for Go.<p>I also felt that Go errors where too bare-bones, so I developed a small package (<a href="https:&#x2F;&#x2F;github.com&#x2F;Vanclief&#x2F;ez">https:&#x2F;&#x2F;github.com&#x2F;Vanclief&#x2F;ez</a>) based on an awesome post that I saw here once. I use this package in all Golang code I touch.

We actually did something similar in Go here: <a href="https:&#x2F;&#x2F;github.com&#x2F;Bedrock-OSS&#x2F;go-burrito">https:&#x2F;&#x2F;github.com&#x2F;Bedrock-OSS&#x2F;go-burrito</a><p>I guess the difference we try to make is that we really wanted to make errors that are understandable by users. Each time the error is returned we try to wrap it with an information where and why.

(Aside about Zig, sorry. Although this applies to Go as well, I think?) Urgh I am <i>so</i> keen to switch to Zig but their attitude towards having vector operators just completely kills the viability for me as a graphics programmer.<p>I&#x27;ve asked in their Discord, Andrew Kelley himself passed on commenting (I know his stance, every C++ dev wants their fav feature), but the reality remains that it&#x27;s just infeasible to do with a DSL so it&#x27;s just the wrong language for writing graphics code.

Can you explain why we should this over <a href="https:&#x2F;&#x2F;github.com&#x2F;pkg&#x2F;errors">https:&#x2F;&#x2F;github.com&#x2F;pkg&#x2F;errors</a>?

go is step by step reinventing exceptions