Re:Low-Level Optimization with Zig
by kbolino on Saturday June 07, 2025 @10:56AM
(#44210071)
The way Zig addresses it also discards all of the runtime variability too. In Go, an error can say something like
Whereas in Zig, an error can only say something that's known at compile time, like IntParse, and you will have to use another mechanism (e.g. logging) to actually trace the error.
[ Parent
| on HN ]
Re:Low-Level Optimization with Zig
by metaltyphoon on Saturday June 07, 2025 @09:36PM
(#44213945)
Yep. Errors carry no context whatsoever and you have no idea where they came from.
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...