There are plans in Zig to allow to include custom information into error stack trace https://github.com/ziglang/zig/issues/14446 https://github.com/ziglang/zig/

There are plans in Zig to allow to include custom information into error stack trace https://github.com/ziglang/zig/issues/14446 https://github.com/ziglang/zig/issues/14446. But that is not implemented. In any case, when debugging annotating error with extra context often is not enough. One often needs a detailed trace of what happens before. So what I would like to see in any programming language is ability to do a structured logging with extra context from the call stack (including asynchronous support in languages that have that) that has almost zero overhead when the log is not printed. Various languages and runtimes have some libraries that try to do that, but the usage is awkward and the performance overhead is not trivial.