You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to #1388. If the standard library ever do change the memory layout of SocketAddr, usage of this crate of versions before 0.7.6 will have undefined behaviour and lead to segfaults. And even if the standard library never do change the layout of those types, those older versions of this crate still makes assumptions they should not.
This is exactly what yanking is for. Marking a release as "should not be used". I think all versions of mio from 0.7.0 through 0.7.5 should be yanked from crates.io.
Due to #1388. If the standard library ever do change the memory layout of
SocketAddr
, usage of this crate of versions before0.7.6
will have undefined behaviour and lead to segfaults. And even if the standard library never do change the layout of those types, those older versions of this crate still makes assumptions they should not.This is exactly what yanking is for. Marking a release as "should not be used". I think all versions of
mio
from0.7.0
through0.7.5
should be yanked from crates.io.Related issues on other crates having the same problem: deprecrated/net2-rs#107, rust-lang/socket2#139
The text was updated successfully, but these errors were encountered: