Jon Gjengset

I believe some of the confusion about "why doesn't `cargo-outdated` show me `X`" also stems from https://github.com/kbknapp/cargo-outdated/issues/134, which I just stumbled upon.

Just leaving a note here that cargo tree was recently adopted into cargo proper in https://github.com/rust-lang/cargo/pull/8062, which, at least to me, indicates that it's not impossible the same may happen...

@alexcrichton #3870 was closed with > we may wish to continue to discuss this externally outside of a PR before resubmitting. Has any more discussion taken place?

To build on this, it would be handy to have a way of declaring dependencies for only *some* binaries. For example, I have one binary that does EC2 orchestration, and...

Some quick thoughts on this: **Restrictions on the path.** What's the motivation for restricting the paths? Cargo potentially having special files in `.cargo/` in the future is a good one,...

> * This setup must be optional (e.g. no warnings when included files are not existing). Why must it produce no warnings? > * paths (see above) or other default...

`std::task` _should_ work fine on WASM I believe, and I don't think there's anything else in the crate that _requires_ that you run on an OS directly. You will need...

I'd be happy to accept a PR that adds an example! The basic idea is that you use `AsyncBincodeX` to wrap a `AsyncX` (e.g., `AsyncBincodeReader` to wrap a type that...

You need to have some type that implements `AsyncRead`, say a `socket`, and then you do `AsyncBincodeReader::from(socket)`. The thing you get back you can then use as a `Stream`.

I'm hoping to get back to this at some future as part of my [live-coding streams](https://www.youtube.com/c/JonGjengset), which is where [we built](https://www.youtube.com/watch?v=RBQwZthJjoM) what's here already. You can vote for that particular...