Release 0.3.2 should be 0.4.0

[jsancio]

I believe that when PR #2049 was merged and release it should be consider a breaking change since it changed the semantic of FutureUnordered::poll_next.

This is cargo's version semantic:

This compatibility convention is different from SemVer in the way it treats versions before 1.0.0. While SemVer says there is no compatibility before 1.0.0, Cargo considers 0.x.y to be compatible with 0.x.z, where y ≥ z and x > 0.

I think this means that release 0.3.2 should have really been versioned as 0.4.0.

It is probably already too late to do anything.

[jonhoo]

I don't think it is a breaking change, since FuturesUnordered still follows the contract of Future::poll. Does my answer in #2049 (comment) help, or is there some other breakage you are thinking of?

[jsancio]

Agree, not a breaking change based on the comments above.