[metaltyphoon]

Yep. Errors carry no context whatsoever and you have no idea where they came from.

[Zambyte]

You can trace error returns with the builtin @errorReturnTrace function.

https://ziglang.org/documentation/0.14.1/#errorReturnTrace

https://ziglang.org/documentation/0.14.1/#Error-Return-Trace...

[gf000]

I mean, this is definitely not a strong suit of go either. In Zig you can just pass in a pointer though to add additional context.