hey, would you be interested in feature-gating this to act as a facade so std would expose the standard library types and not(std) would expose the local crate types? this would make it easier to write libraries that are agnostic over std/no_std, but still work with third party networking components in the std case.
this would be useful prior to rust-lang/rfcs#2832 landing and being implemented, and for types not included in this RFC (SocketAddr etc.)
nominally it would be good to test to ensure each variant provides the same interfaces as part of this (and any variation in interfaces would ideally be resolved, which may be a braking change), but practically introducing the feature-gate without anything else would still help a bunch.
hey, would you be interested in feature-gating this to act as a facade so
stdwould expose the standard library types andnot(std)would expose the local crate types? this would make it easier to write libraries that are agnostic over std/no_std, but still work with third party networking components in the std case.this would be useful prior to rust-lang/rfcs#2832 landing and being implemented, and for types not included in this RFC (
SocketAddretc.)nominally it would be good to test to ensure each variant provides the same interfaces as part of this (and any variation in interfaces would ideally be resolved, which may be a braking change), but practically introducing the feature-gate without anything else would still help a bunch.