Think some more about SIGPIPE handling

[unflxw]

See also Slack monologue.

I'm not sure the current approach is right. I think we want is not the current reset_sigpipe reset, but #[unix_sigpipe = "inherit"], which is an experimental feature, available only on nightly.

Child processes will inherit whatever we set, and without #[unix_sigpipe = "inherit"], the child process will always have something (by default, "ignore") set on its behalf by the Rust standard library, so our options become:

Break the behaviour of some child processes when used in pipes (without reset_sigpipe)
Break the behaviour of some child processes when used in systemd (with reset_sigpipe)

I care a lot more about the systemd use case than about the pipes use case, so the options I’m considering are “remove reset_sigpipe” or “use a nightly toolchain”.

[backlog-helper]

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

[unflxw]

For now, I think I'm going to remove reset_sigpipe, therefore restoring the Rust standard library's default behaviour, which is to ignore it, and not do any special handling of SIGPIPE -- that is, not forward it to the child process either, which will instead inherit the ignoring behaviour.

This seems preferable to the alternative.

[unflxw]

Closing this for now -- #18 changes the application as described in the previous comment.