mirror of
https://codeberg.org/ziglang/zig
synced 2026-11-18 07:05:05 +00:00
It doesn't make any sense for a task to be canceled while it's panicking. As a happy accident, this also solves some cases where safety panics in `Io.Threaded` would cause stack traces not to print due to invalid thread-local state: when cancelation is blocked, `Io.Threaded` doesn't consult said thread-local state at all. For instance, try inserting a panic just after a call to `Syscall.start()` in `Io.Threaded`, and then call the `Io` function in question from a `concurrent` task. Before this PR, the stack trace fails to print, because the panic handler sees the thread-local cancelation state in an unexpected state, leading to a recursive panic. After this PR, the stack trace prints fine.
1764 lines
71 KiB
1764 lines
71 KiB