Chris Copeland b02698c7e6 use BOOL for TCP_NODELAY setsockopt value on Windows ... This issue was found by the Wine project and mitigated there [1]. Windows' documented interface for `setsockopt` expects a `BOOL` (a `typedef` for `int`) for `TCP_NODELAY` [2]. Windows is forgiving and will accept any positive length and interpret the first byte of `*option_value` as the value, so this bug does not affect Windows itself, but does affect systems implementing Windows' interface more strictly, such as Wine. Wine was previously passing this through to the host's `setsockopt`, where, e.g., Linux requires that `option_len` be correct for the chosen option, and `TCP_NODELAY` expects an `int`. [1]: d6ea38f32d [2]: https://docs.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-setsockopt		2022-02-20 21:27:36 -08:00
..
benches
primitive_docs	Add primitive documentation to libcore	2021-09-12 02:23:08 +00:00
src	use BOOL for TCP_NODELAY setsockopt value on Windows	2022-02-20 21:27:36 -08:00
tests	Move is_aarch64_feature_detected! to simd_aarch64 feature and stabilise	2022-02-10 15:24:13 +00:00
build.rs	std: Get the standard library compiling for wasm64	2021-11-10 08:35:42 -08:00
Cargo.toml	removing architecture requirements for RustyHermit	2022-02-15 13:57:07 +01:00