onurzdg / mio-misc Goto Github PK

Hi,

It looks like mio is a public dependency of mio-misc. Which means bumping to 0.8 was a breaking change, but has been released as part of the 1.3.2 patch.

This resulted in breakage in other projects. For example bevy (on linux):

git clone https://github.com/bevyengine/bevy.git
cd bevy
git checkout 2abf5cc618957ed6a2acf6a496c0039513746cae
cargo update
cargo check --workspace # <-- Compilation error due to semver incompatibility

Could you yank 1.3.2 and release your changes as 2.0.0 instead?

hi there, i'm looking at migrating a crate from mio 0.6 -> 0.7. This also necessitates (I believe) migrating from mio-extras to mio-misc.

The crate uses mio_extras::channel::Receiver, which implements mio 0.6's mio::Evented. The equivalent trait in mio 0.7, mio::event::Source is not implemented for the Receiver type in mio-misc which is a re-export of std::sync::mspc::Receiver.

how should these be reconciled?

for reference, the crate is here - https://github.com/jhelovuo/RustDDS