|
Returning error codes across the C ABI
|
|
3
|
161
|
June 20, 2025
|
|
JS-like errors in Zig
|
|
11
|
363
|
June 6, 2025
|
|
Should there be a shortcut for `catch |err| @panic(@errorName(err))`?
|
|
10
|
353
|
May 15, 2025
|
|
Preserve error return traces across Zig-C-Zig calls
|
|
1
|
123
|
March 30, 2025
|
|
Errdefer scoped to the parent block
|
|
3
|
179
|
February 3, 2025
|
|
How to handle optional functions causing unreachable in the header of a while loop?
|
|
11
|
154
|
January 28, 2025
|
|
Displaying error messages
|
|
13
|
235
|
November 26, 2024
|
|
New to Zig. Having issues understanding the compiler warnings. (Error handling and function returns)
|
|
12
|
461
|
November 17, 2024
|
|
What if compiler didn't allow variables that can contain error unions?
|
|
15
|
232
|
October 7, 2024
|
|
Zig-recover - Regain control when a function panics
|
|
4
|
900
|
August 29, 2024
|
|
Idiomatic way to emit errors during build?
|
|
17
|
465
|
August 8, 2024
|
|
Iterating optional error unions (i.e. `!?T`)
|
|
12
|
258
|
July 19, 2024
|
|
Std.mem.eql seems to crash my kernel in a weird way
|
|
5
|
212
|
May 3, 2024
|
|
How to handle errors with less nesting?
|
|
3
|
218
|
April 18, 2024
|
|
Using ComptimeStringMap for Errors with Payloads
|
|
20
|
1049
|
March 21, 2024
|
|
Applying the Diagnostics pattern in practice
|
|
1
|
604
|
March 17, 2024
|
|
How to solve error "unable to resolve comptime value"?
|
|
8
|
1808
|
March 7, 2024
|
|
What is the best way to handle unrecoverable errors like OutOfMemory in an application?
|
|
25
|
1551
|
January 29, 2024
|
|
Error code disambiguation / specializing
|
|
5
|
410
|
January 28, 2024
|
|
Error handling (with custom messages)
|
|
4
|
475
|
December 31, 2023
|
|
Custom errors with payloads (with current zig)
|
|
6
|
1963
|
December 18, 2023
|