David Kellum

Somewhat related to the process outlined by @Eh2406 above... As a prerelease exercise, I maintain and check in a Cargo.lock on a dedicated minimal-versions branch. The maintenance of that lock...

FWIW: In my active projects, including a public crate with Cargo.lock below, I've avoided updates to rand for ~5 months now, while taking other updates, due to induced duplicates (rand-core...

It would seem that `cargo -Z minimal-versions generate-lockfile` should be aware of, and lock results conditional upon, what features are selected either by default, or via additional feature arguments to...

Hi, have you considered the implications of doing compress/decompress on the reactor thread vs. some other coordination strategy or dispatching to non-reactor thread? Good benchmarks should be able to inform...

If you go so far as to benchmark compression of HTTP bodies to/from the network with some amount of concurrency (a full stack kind of simulation), then you might want...

There might be other issues as well (Systest?) but I can reliably reproduce the problem found for macos on CI (on linux in my case): ``` Running `target/release/examples/all-read-write-roundtrips` thread 'main'...

Thanks, I hope you don't mind me keeping this open while I'm trying to find a fix! If I get anywhere and continue using it, I'll definitely request maintenance permissions.

Talking similar potential features with the *Gotham* developers. There is also https://github.com/scottlamb/http-serve which has been updated to hyper 0.12.

Hyper 0.12 has been released. Sufficient?

Yep, that will be a major refactor for body-image (currently on tokio 0.1.x and futures 0.1.x ) as well.