didc panics if I redirect output to a file with `<(...)` syntax

$ echo <(/home/omer/dfinity/candid/target/debug/didc encode ...)
/proc/self/fd/11
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }', tools/didc/src/main.rs:245:52
stack backtrace:
$    0: rust_begin_unwind
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/panicking.rs:493:5
   1: std::panicking::begin_panic_fmt
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/panicking.rs:435:5
   2: std::io::stdio::print_to
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/io/stdio.rs:940:9
   3: std::io::stdio::_print
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/io/stdio.rs:952:5
   4: didc::main
             at /home/omer/dfinity/candid/tools/didc/src/main.rs:244:13
   5: core::ops::function::FnOnce::call_once
             at /home/omer/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Trying with current master branch (a555d77704d691bb8f34e21a049d44ba0acee3f8)

Start with tools/didc/src/main.rs around lines 244-245 and reproduce the issue using the reported didc command with <(...) output redirection. Check how output errors are handled when the pipe closes. Done means the same invocation no longer panics with a Broken pipe error.