Re: [PATCH] t5512.40 sometimes dies by SIGPIPE

Chris Torek [off-list ref] writes:

It's more complicated than that (and varies on MacOS), but it's true
that the Go runtime wraps all OS-level write() operations. The reason
for that is that Go has its own internal "thread" (g/m/p things, really)
scheduler and does *all* I/O as non-blocking calls. Anything that
potentially blocks an actual OS-level thread has to be handled
specially. It's quite messy and You Don't Want To Go There (no
pun intended) if you don't have to.

That sounds like a fun hack ;-)