Nemo157

I think having the functionality of `tokio-codec` is definitely going to be important for trying out `romio`, but as @withoutboats mentions this isn’t specific to the low-level IO primitives. Since...

(One thing I'm not sure about with that wrapper is whether `TcpStream::shutdown` can return `WouldBlock`, if so then it would need to hook into the reactor somehow).

@jwodder before you get too deep in with cargo-lichking, I should mention I've been meaning to explicitly deprecate it for a while. There are other existing tools that cover most...

`lichking` is using `cargo metadata` to get the info, but there's definitely the chance it's over-zealous in which packages it pulls out of that. With `cargo metadata --all-features | jq...

Oh, turns out `cargo tree` does support it, it's just undocumented :grin: ```console > cargo tree --target all -i arrayref arrayref v0.3.6 └── blake2b_simd v0.5.10 └── rust-argon2 v0.7.0 └── redox_users...

Sounds like a good idea.

By copyright holder I presume you mean the _actual_ copyright holders, not just the authors listed in the crate metadata or license files that have them? That would be significantly...

This looks like a bit to take in, I'll try and take a look in the next day or two. cc @jrobsonchase in case you have any feedback as well.

I believe the main point of this compatibility checking is to say > If I license my crate under license A and pull in a dependency under license B, does...

> This interpretation is valuable to library authors, but it's incomplete to application authors [...] This is a good point. I'll try and find some time this week to work...