Skip to content

Comment on Zig’s Io.Threaded is neatparent

Comments

I think that specific issue was a huge mistake, because it means the interruption, which was already messy, is now unusable.

First, you can get deadlocks as interrupt now calls arbitrary code to close channels. Second the interruptee thread cannot recover from an interrupt, if it chooses to to. Lastly it means that a server that shares a file descriptor with multiple threads breaks unrelated operations on interruption.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.