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

Age	Commit message (Collapse)	Author	Lines
2015-01-21	syntax: fix fallout of merging ast::ViewItem into ast::Item.	Eduard Burtescu	-32/+4

2015-01-04	Add syntax for negative implementations of traits	Flavio Percoco	-2/+2
	This commit introduces the syntax for negative implmenetations of traits as shown below: `impl !Trait for Type {}` cc #13231 Part of RFC #3
2014-12-26	Accept `?Sized` as well as `Sized?`	Nick Cameron	-2/+2
	Includes a bit of refactoring to store `?` unbounds as bounds with a modifier, rather than in their own world, in the AST at least.
2014-12-14	Parse `unsafe impl` but don't do anything particularly interesting with the ↵	Niko Matsakis	-2/+2
	results.
2014-12-14	Parse `unsafe trait` but do not do anything with it beyond parsing and ↵	Niko Matsakis	-2/+2
	integrating into rustdoc etc.
2014-12-13	libsyntax: use unboxed closures	Jorge Aparicio	-23/+59

2014-11-25	Fallout from stabilization	Aaron Turon	-2/+1

2014-11-07	rustc: Process #[cfg]/#[cfg_attr] on crates	Alex Crichton	-7/+16
	This commit implements processing these two attributes at the crate level as well as at the item level. When #[cfg] is applied at the crate level, then the entire crate will be omitted if the cfg doesn't match. The #[cfg_attr] attribute is processed as usual in that the attribute is included or not depending on whether the cfg matches. This was spurred on by motivations of #18585 where #[cfg_attr] annotations will be applied at the crate-level. cc #18585
2014-10-25	Finish cfg syntax transition	Steven Fackler	-17/+5

2014-10-13	auto merge of #17963 : sfackler/rust/cfg-error, r=alexcrichton	bors	-8/+8
	All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and".
2014-10-12	Continue cfg syntax transition	Steven Fackler	-8/+8
	All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and".
2014-10-11	Remove `virtual` structs from the language	Jakub Wieczorek	-3/+1

2014-10-01	auto merge of #17630 : sfackler/rust/cfg-warnings, r=brson	bors	-3/+0
	Closes #17490
2014-09-30	Turn on cfg format warnings	Steven Fackler	-3/+0

2014-09-30	Produce a better error for irrefutable `if let` patterns	Kevin Ballard	-2/+2
	Modify ast::ExprMatch to include a new value of type ast::MatchSource, making it easy to tell whether the match was written literally or produced via desugaring. This allows us to customize error messages appropriately.
2014-09-27	Convert cfg syntax to new system	Steven Fackler	-4/+33
	This removes the ability to use `foo(bar)` style cfgs. Switch them to `foo_bar` or `foo="bar"` instead. [breaking-change]
2014-09-17	librustc: Implement associated types behind a feature gate.	Patrick Walton	-1/+3
	The implementation essentially desugars during type collection and AST type conversion time into the parameter scheme we have now. Only fully qualified names--e.g. `<T as Foo>::Bar`--are supported.
2014-09-17	move most of front to libsyntax	Nick Cameron	-0/+253