rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2019-03-31	libstd: deny(elided_lifetimes_in_paths)	Mazdak Farrokhzad	-3/+3

2019-03-16	Add UdpSocket peer_addr implementation for L4Re	Linus Unnebäck	-1/+4

2019-03-09	Use lifetime contravariance to elide more lifetimes in core+alloc+std	Scott McMurray	-2/+2

2019-02-28	libstd => 2018	Taiki Endo	-9/+9

2019-02-13	Add vectored read and write support	Steven Fackler	-1/+17
	This functionality has lived for a while in the tokio ecosystem, where it can improve performance by minimizing copies.
2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-12-06	Refactor net::each_addr/lookup_host to forward error from resolve	Jethro Beekman	-7/+26

2018-01-16	Only link res_init() on GNU/*nix	Ryan Cumming	-4/+0
	To workaround a bug in glibc <= 2.26 lookup_host() calls res_init() based on the glibc version detected at runtime. While this avoids calling res_init() on platforms where it's not required we will still end up linking against the symbol. This causes an issue on macOS where res_init() is implemented in a separate library (libresolv.9.dylib) from the main libc. While this is harmless for standalone programs it becomes a problem if Rust code is statically linked against another program. If the linked program doesn't already specify -lresolv it will cause the link to fail. This is captured in issue #46797 Fix this by hooking in to the glibc workaround in `cvt_gai` and only activating it for the "gnu" environment on Unix This should include all glibc platforms while excluding musl, windows-gnu, macOS, FreeBSD, etc. This has the side benefit of removing the #[cfg] in sys_common; only unix.rs has code related to the workaround now.
2017-10-05	replace libc::res_init with res_init_if_glibc_before_2_26	Jack O'Connor	-0/+4
	The previous workaround for gibc's res_init bug is not thread-safe on other implementations of libc, and it can cause crashes. Use a runtime check to make sure we only call res_init when we need to, which is also when it's safe. See https://github.com/rust-lang/rust/issues/43592.
2017-09-13	Move default stack min size to thread implementations	Tobias Schaffner	-2/+2
	The default min stack size value is smaller on l4re and therefore this value has to be different depending on the platform.
2017-09-08	Re-enable networking module fo rL4Re	Sebastian Humenda	-0/+441
	As suggested in the discussion of PR #43972, std should provide a uniform API to all platforms. Since there's no networking on L4Re, this now is a module in `sys::net` providing types and functions/methods returning an error for each action.