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

Age	Commit message (Collapse)	Author	Lines
2017-11-04	rustc: Handle some libstd symbole exports better	Alex Crichton	-0/+4
	Right now symbol exports, particularly in a cdylib, are handled by assuming that `pub extern` combined with `#[no_mangle]` means "export this". This isn't actually what we want for some symbols that the standard library uses to implement itself, for example symbols related to allocation. Additionally other special symbols like `rust_eh_personallity` have no need to be exported from cdylib crate types (only needed in dylib crate types). This commit updates how rustc handles these special symbols by adding to the hardcoded logic of symbols like `rust_eh_personallity` but also adding a new attribute, `#[rustc_std_internal_symbol]`, which forces the export level to be considered the same as all other Rust functions instead of looking like a C function. The eventual goal here is to prevent functions like `__rdl_alloc` from showing up as part of a Rust cdylib as it's just an internal implementation detail. This then further allows such symbols to get gc'd by the linker when creating a cdylib.
2017-08-30	Make fields of `Span` private	Vadim Petrochenkov	-4/+1

2017-08-19	rustc: Remove some dead code	Vadim Petrochenkov	-11/+2

2017-08-15	use field init shorthand EVERYWHERE	Zack M. Davis	-4/+4
	Like #43008 (f668999), but _much more aggressive_.
2017-08-12	syntax: #[allow_internal_unsafe] bypasses the unsafe_code lint in macros.	Eduard-Mihai Burtescu	-0/+1

2017-08-01	Fixed all unnecessary muts in language core	Isaac van Bakel	-2/+2

2017-07-05	rustc: Implement the #[global_allocator] attribute	Alex Crichton	-0/+614
	This PR is an implementation of [RFC 1974] which specifies a new method of defining a global allocator for a program. This obsoletes the old `#![allocator]` attribute and also removes support for it. [RFC 1974]: https://github.com/rust-lang/rfcs/pull/197 The new `#[global_allocator]` attribute solves many issues encountered with the `#![allocator]` attribute such as composition and restrictions on the crate graph itself. The compiler now has much more control over the ABI of the allocator and how it's implemented, allowing much more freedom in terms of how this feature is implemented. cc #27389