Taiki Endo

> Rust 1.60 introduced a new feature for test coverage. Can we use it? cargo-llvm-cov (v0.2+) uses `-C instrument-coverage` that stabilized in 1.60. (v0.1 uses `-Z instrument-coverage` that is old...

> heavy Is this still a problem even if the next version of futures-util is released? (https://github.com/rust-lang/futures-rs/pull/2273) If it can solve the problem, I can publish it. (Also, note that...

fyi https://github.com/rust-lang/futures-rs/pull/2307

I think we can close this as futures-util [0.3.9](https://github.com/rust-lang/futures-rs/releases/tag/0.3.9) has been released. (All of the main users of this crate seem to depend on futures-util, so adding a dependency like...

Probably related: https://github.com/rust-lang/rust/issues/28129

Thanks for the PR! The situation is almost the same as [before](https://github.com/openrr/k/issues/66#issuecomment-905203444). There are three major options we can choose from: The first (regular) way is to update ncollide to...

As said in https://github.com/tokio-rs/bytes/issues/461#issuecomment-763360588, I don't think it's possible without breaking changes. See also https://github.com/crossbeam-rs/crossbeam/pull/508#discussion_r427969049.

The main problem is that we recently released v1 and don't want to release v2 right away. > Since this issue was know before first major release maybe "not make...

> There is a way to achieve embedded compatibility (and I hope MSRV 1.36) without breaking `bytes` API: jut move the traits only to a separate `bytes-traits` crate and reexport/implement...

@Kixunil "the old version of bytes crate" meant the 1.x.y version that does not contain the changes you suggested. They are different traits in the 1.x.y version that does not...