Pascal Hertleif

Crates we can help: - get assert_cli to 1.0 (@killercup and @epage) - get dir-diff to 1.0 (@steveklabnik)

We've been talking about integration testing for a bit [on gitter](https://gitter.im/rust-lang/WG-CLI?at=5a99806be4ff28713ae733bb). I've created the [assert-rs](https://github.com/assert-rs) github organization and moved assert_cli there.

> A topic that comes to mind is non-blocking reads/writes to stdin/stdout. Oh, very good point! We should look into this. I don't know what the tokio ecosystem has in...

We might also want to mention https://github.com/sharkdp/hyperfine and https://github.com/ferrous-systems/flamegraph

Very true! That's also the only performance hint the book currently [contains](https://rust-lang-nursery.github.io/cli-wg/tutorial/output.html#a-note-on-printing-performance) ;)

One idea, championed by @vitiral is to provide an "extended std lib" that collects a bunch of useful crates and exposes them with a unified API surface. Implementation is currently...

Another idea is to use cargo templates ([Pre-RFC](https://internals.rust-lang.org/t/pre-rfc-cargo-templates/5056)) to help new users get started by providing them a project setup that already contains a bunch of tooling.

@djhworld very good point! I have a TODO open for stdin in #95. I'm not entirely sure what the book should recommend precisely; I'd say using a buffered reader is...

@yuvadm I haven't seen a write-up about it, but I'd love to see one! :) Maybe have a look at what some projects use? Reading and writing to std{in,out} should...

Thanks for opening this! One of the goals of this WG should be to have a best-pratice list like this including source code example in Rust :)