Consider coordinating tokio-io / bytes releases about tokio HOT 9 CLOSED

What breaking changes are planned? Any pointers?

from tokio.

I haven't made a full inventory of breaking changes yet. Each crate should get a milestone to track.

I don't think that the bytes crate has anything major. The biggest is changing some IntoBuf impls to get rid of Cursor.

iovec needs to a breaking change to better address the soundness issue that was discovered and fixed in 0.1.1.

Off the top of my head, I don't think that tokio-io has any breaking changes itself, but it needs to bump the version since it re-exports bytes and iovec types.

from tokio.

I also think BufMut should have put_* methods documented to grow buffer, as well as the implementation for BytesMut (this is a sort of extension to tokio-rs/bytes#131 which is marked as 0.5-blocker).

from tokio.

I put some commentary on blocking 0.1 here.

from tokio.

Off the top of my head, I don't think that tokio-io has any breaking changes itself,

It'd be nice to have an opportunity to do this (although I agree with @aturon that 0.2 can wait until after 0.1 of this crate. I think it should coincide with pending futures-rs/mio/bytes/iovec breaking changes).

from tokio.

I believe that the current plan is to only release tokio 0.1 and then coordinate an ecosystem bump after that.

from tokio.

@carllerche Do you mean tokio 0.2?

from tokio.

Nope tokio 0.1!

from tokio.

@carllerche Oh, I see, you mean of the tokio crate, not tokio-core.

from tokio.