4 ms·
Note that this "diagnostics" pattern is only meant for handling a error locally with potential extra information, or showing a more useful error to a end user o
by Cloudef 8mo ago
Note that this "diagnostics" pattern is only meant for handling a error locally with potential extra information, or showing a more useful error to a end user of the software. For software bugs, crashes, or developer facing errors, you often don't have to do anything as zig has pretty good error traces by default.
- andyferris 8mo ago> stacktraces are only available in certain build modes > zig has pretty good error traces by default These seem rather conditional. If I need to run release-fast in prod, say, do we loose these error traces (for bugs)?
- messe 8mo agoYou do, to a significant extent. Though there is always the option of running ReleaseSafe.
- Cloudef 8mo agoYou can enable error traces for release-fast builds as well, without enabling full debug info. Though the quality of call stack of course vary depending on optimization level.
- dnautics 8mo agooh awesome. I thought error traces were only on debug and optionally on ReleaseSafe.