Yuki Okushi d340f63cca Rollup merge of #83524 - faern:document-socketaddr-mem-layout, r=sfackler ... Document that the SocketAddr memory representation is not stable Intended to help out with #78802. Work has been put into finding and fixing code that assumes the memory layout of `SocketAddrV4` and `SocketAddrV6`. But it turns out there are cases where new code continues to make the same assumption ([example](96927dc2b7 (diff-917db3d8ca6f862ebf42726b23c72a12b35e584e497ebdb24e474348d7c6ffb6R610-R621))). The memory layout of a type in `std` is never part of the public API. Unless explicitly stated I guess. But since that is invalidly relied upon by a considerable amount of code for these particular types, it might make sense to explicitly document this. This can be temporary. Once #78802 lands it does not make sense to rely on the layout any longer, and this documentation can also be removed.		2021-03-27 12:37:24 +09:00
..
benches	mv std libs to library/	2020-07-27 19:51:13 -05:00
src	Rollup merge of #83524 - faern:document-socketaddr-mem-layout, r=sfackler	2021-03-27 12:37:24 +09:00
tests	Fix SGX CI, take 3	2020-12-07 15:22:34 +01:00
build.rs	Drop support for cloudabi targets	2020-11-22 17:11:41 -05:00
Cargo.toml	feat: Update hashbrown to instantiate less llvm IR	2021-03-16 11:20:26 +01:00