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
The core::net module is heading for stabilization. It's currently stable in beta and will be stable in the next stable Rust release (1.77) unless it's reverted for some reason. That's good news, because it means custom crates like this one won't be needed any longer to get basic network primitives in no_std.
I'm not sure if there is any concrete action for this crate to take once the stabilization happens. Dynamic rustc version detection to determine if the crate should just act as a facade or not can be a bit iffy, and also does not come without a bunch of dependencies just for said detection.
There can probably be a readme update advising people to use core::net instead, if their MSRV allows it.
The text was updated successfully, but these errors were encountered:
faern
changed the title
core::net soon to be stable!core::net is stable. This library is obsolete?
Apr 23, 2024
It would be nice if this crate could reexport the core types, so that other crates that are using this one automatically get updated to core types (of course after an acceptable MSRV period).
The
core::net
module is heading for stabilization. It's currently stable in beta and will be stable in the next stable Rust release (1.77) unless it's reverted for some reason. That's good news, because it means custom crates like this one won't be needed any longer to get basic network primitives inno_std
.I'm not sure if there is any concrete action for this crate to take once the stabilization happens. Dynamic
rustc
version detection to determine if the crate should just act as a facade or not can be a bit iffy, and also does not come without a bunch of dependencies just for said detection.There can probably be a readme update advising people to use
core::net
instead, if their MSRV allows it.The text was updated successfully, but these errors were encountered: