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

Age	Commit message (Collapse)	Author	Lines
2016-10-18	Fix some pretty printing tests	Vadim Petrochenkov	-1/+1

2016-05-06	s/aux/auxiliary, because windows	Niko Matsakis	-2/+2
	For legacy reasons (presumably), Windows does not permit files name aux.
2016-05-06	kill the old auxiliary directory	Niko Matsakis	-2/+2

2015-02-18	Update suffixes en masse in tests using `perl -p -i -e`	Niko Matsakis	-1/+1

2014-12-18	librustc: Always parse `macro!()`/`macro![]` as expressions if not	Patrick Walton	-1/+1
	followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change]
2014-11-03	Test fixes and rebase conflicts	Alex Crichton	-0/+2

2014-10-30	rustc: Implement -l and include! tweaks	Alex Crichton	-0/+18
	This is an implementation of the rustc bits of [RFC 403][rfc]. This adds a new flag to the compiler, `-l`, as well as tweaking the `include!` macro (and related source-centric macros). The compiler's new `-l` flag is used to link libraries in from the command line. This flag stacks with `#[link]` directives already found in the program. The purpose of this flag, also stated in the RFC, is to ease linking against native libraries which have wildly different requirements across platforms and even within distributions of one platform. This flag accepts a string of the form `NAME[:KIND]` where `KIND` is optional or one of dylib, static, or framework. This is roughly equivalent to if the equivalent `#[link]` directive were just written in the program. The `include!` macro has been modified to recursively expand macros to allow usage of `concat!` as an argument, for example. The use case spelled out in RFC 403 was for `env!` to be used as well to include compile-time generated files. The macro also received a bit of tweaking to allow it to expand to either an expression or a series of items, depending on what context it's used in. [rfc]: https://github.com/rust-lang/rfcs/pull/403