7 releases (stable)
|1.4.0||Nov 15, 2020|
|1.3.0||Aug 22, 2020|
|1.1.0||Jul 27, 2020|
|1.0.1||Feb 7, 2020|
|0.1.1||Feb 5, 2020|
#141 in Command-line interface
133 downloads per month
Used in 2 crates
A Mux provides a single receive end and multiple send ends. Data sent to any of the send ends comes out the receive end, in order, tagged by the sender.
Each send end works as a file descriptor. For instance, with
io-mux you can
collect stdout and stderr from a process, and highlight any error output from
stderr, while preserving the relative order of data across both stdout and
If you enable the
io-mux additionally provides an
type, which allows processing data asynchronously.
You may want to use this with
async-pidfd to concurrently wait on the
exit of a process and the muxed output and error of that process. Until the
process exits, call
AsyncMux::read() to get the next bit of output, awaiting
that concurrently with the exit of the process. Once the process exits and will
thus produce no further output, call
AsyncMux::read_nonblock until it returns
None to drain the remaining output out of the mux.
io-mux uses UNIX sockets, so it only runs on UNIX platforms. Support for
non-Linux platforms is experimental, and has a major caveat in its semantics;
please see the documentation for more details.