Due to #106. If the standard library ever do change the memory layout of SocketAddr, usage of this crate of versions before 0.2.36 will have undefined behaviour and invalid memory access and lead to segfaults. And even if the standard library never do change the layout of those types, those 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 net2 from 0.2.0 through 0.2.35 should be yanked from crates.io.
Related issues on other crates having the same problem: rust-lang/socket2#139, tokio-rs/mio#1412
Due to #106. If the standard library ever do change the memory layout of
SocketAddr, usage of this crate of versions before0.2.36will have undefined behaviour and invalid memory access and lead to segfaults. And even if the standard library never do change the layout of those types, those 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
net2from0.2.0through0.2.35should be yanked from crates.io.Related issues on other crates having the same problem: rust-lang/socket2#139, tokio-rs/mio#1412