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

Age	Commit message (Collapse)	Author	Lines
2015-10-13	Merge struct fields and struct kind	Vadim Petrochenkov	-1/+1

2015-10-13	Dict -> Struct, StructDef -> VariantData, def -> data	Vadim Petrochenkov	-1/+1

2015-10-13	Decouple structure kinds from NodeIds	Vadim Petrochenkov	-1/+1

2015-10-13	Unify structures and enum variants in AST	Vadim Petrochenkov	-35/+25

2015-08-29	Allow #[derive()] to generate unsafe trait impls	Michael Layzell	-0/+1

2015-05-22	Let MultiItemDecorator take `&Annotatable` (fixes #25683)	Manish Goregaokar	-2/+2

2015-05-17	Allow #[derive()] to generate unsafe methods	Manish Goregaokar	-0/+2

2015-05-12	Rebasing	Nick Cameron	-1/+1

2015-04-30	WIP refactor expansion of decorators and move derive to MultiDecorator	Nick Cameron	-4/+4

2015-04-21	syntax: Remove uses of #[feature(slice_patterns)]	Erick Tryzelaar	-2/+2

2015-04-21	syntax: remove #![feature(box_syntax, box_patterns)]	Erick Tryzelaar	-2/+2

2015-04-15	syntax: Change deriving methods to take a `&mut FnMut(P<Item>)`	Erick Tryzelaar	-6/+5
	This allows #[derive(...)]` to create more than one impl
2015-03-03	Switched to Box::new in many places.	Felix S. Klock II	-4/+4
	Many of the modifications putting in `Box::new` calls also include a pointer to Issue 22405, which tracks going back to `box <expr>` if possible in the future. (Still tried to use `Box<_>` where it sufficed; thus some tests still have `box_syntax` enabled, as they use a mix of `box` and `Box::new`.) Precursor for overloaded-`box` and placement-`in`; see Issue 22181.
2015-02-24	rustc_resolve: use the visitor model more, remove redundant repeated lookups.	Eduard Burtescu	-2/+2

2015-02-12	Made `Self` a keyword.	Marvin Löbel	-2/+2
	It is only allowed in paths now, where it will either work inside a `trait` or `impl` item, or not resolve outside of it. [breaking-change] Closes #22137
2015-02-07	Don't use std:: paths in syntax extensions when compiling a #![no_std] crate	Keegan McAllister	-3/+3
	Fixes #16803. Fixes #14342. Fixes half of #21827 -- slice syntax is still broken.
2015-02-07	Use path helper macros in deriving	Keegan McAllister	-7/+5

2015-02-02	`for x in xs.iter()` -> `for x in &xs`	Jorge Aparicio	-1/+1

2015-01-25	Associated types support for deriving::generic::TraitDef	Dzmitry Malyshau	-1/+3

2015-01-17	s/deriving/derives in Comments/Docs	Earl St Sauver	-2/+2
	There are a large number of places that incorrectly refer to deriving in comments, instead of derives. Fixes #20984
2015-01-05	syntax: remove remaining boxed closures	Jorge Aparicio	-2/+2

2014-12-13	libsyntax: use unboxed closures	Jorge Aparicio	-5/+7

2014-11-17	Switch to purely namespaced enums	Steven Fackler	-1/+2
	This breaks code that referred to variant names in the same namespace as their enum. Reexport the variants in the old location or alter code to refer to the new locations: ``` pub enum Foo { A, B } fn main() { let a = A; } ``` => ``` pub use self::Foo::{A, B}; pub enum Foo { A, B } fn main() { let a = A; } ``` or ``` pub enum Foo { A, B } fn main() { let a = Foo::A; } ``` [breaking-change]
2014-09-14	syntax: fix fallout from using ptr::P.	Eduard Burtescu	-11/+9

2014-07-11	Removed dead structures after changes to PartialOrd/Ord derivings.	Felix S. Klock II	-2/+0
	Remove the `NonMatchesExplode` variant now that no deriving impl uses it. Removed `EnumNonMatching` entirely. Remove now irrelevant `on_matching` field and `HandleNonMatchingEnums` type. Removed unused `EnumNonMatchFunc` type def. Drive-by: revise `EnumNonMatchCollapsedFunc` doc. Made all calls to `expand_enum_method_body` go directly to `build_enum_match_tuple`. Alpha-rename `enum_nonmatch_g` back to `enum_nonmatch_f` to reduce overall diff noise. Inline sole call of `some_ordering_const`. Inline sole call of `ordering_const`. Removed a bunch of code that became dead after the above changes.
2014-07-11	Revise the `const_nonmatching` flag with more info about author's intent.	Felix S. Klock II	-2/+2
	In particular, I want authors of deriving modes to understand what they are opting into (namely quadratic code size or worse) when they select NonMatchesExplode.
2014-06-11	syntax: Move the AST from @T to Gc<T>	Alex Crichton	-4/+7

2014-06-02	syntax: Remove use of `pub use` globs	klutzy	-0/+1
	`quote_expr!` now injects two more (priv) `use` globs. This may cause extra unused_imports warning.
2014-05-02	Replace most ~exprs with 'box'. #11779	Brian Anderson	-2/+2

2014-04-23	auto merge of #12812 : sfackler/rust/attr-arm, r=alexcrichton	bors	-0/+2
	This is really only useful for #[cfg()]. For example: ```rust enum Foo { Bar, Baz, #[cfg(blob)] Blob } fn match_foos(f: &Foo) { match *f { Bar => {} Baz => {} #[cfg(blob)] Blob => {} } } ``` This is a kind of weird place to allow attributes, so it should probably be discussed before merging.
2014-04-23	Allow attributes on match arms	Steven Fackler	-0/+2
	RFC: 0008-match-arm-attributes
2014-04-23	auto merge of #13704 : edwardw/rust/doc-hidden, r=alexcrichton	bors	-4/+6
	Closes #13698
2014-04-23	Fix other bugs with new closure borrowing	Alex Crichton	-2/+6
	This fixes various issues throughout the standard distribution and tests.
2014-04-23	Honor hidden doc attribute of derivable trait methods	Edward Wang	-4/+6
	Closes #13698
2014-03-20	Removing imports of std::vec_ng::Vec	Alex Crichton	-2/+0
	It's now in the prelude.
2014-03-20	rename std::vec_ng -> std::vec	Daniel Micay	-1/+1
	Closes #12771
2014-03-03	syntax: make match arms store the expr directly.	Huon Wilson	-2/+2
	Previously `ast::Arm` was always storing a single `ast::Expr` wrapped in an `ast::Block` (for historical reasons, AIUI), so we might as just store that expr directly. Closes #3085.
2014-03-01	libsyntax: Fix errors arising from the automated `~[T]` conversion	Patrick Walton	-0/+2

2014-03-01	libsyntax: Mechanically change `~[T]` to `Vec<T>`	Patrick Walton	-19/+16

2014-02-21	syntax: Allow syntax extensions to have attributes	Erick Tryzelaar	-0/+1

2014-02-13	Tweak ItemDecorator API	Steven Fackler	-2/+3
	The old method of building up a list of items and threading it through all of the decorators was unwieldy and not really scalable as non-deriving ItemDecorators become possible. The API is now that the decorator gets an immutable reference to the item it's attached to, and a callback that it can pass new items to. If we want to add syntax extensions that can modify the item they're attached to, we can add that later, but I think it'll have to be separate from ItemDecorator to avoid strange ordering issues.
2014-02-08	Update deriving to pass around the `cx` linearly	Niko Matsakis	-3/+2

2014-02-08	Fixed error starting with uppercase	mr.Shu	-1/+1
	Error messages cleaned in librustc/middle Error messages cleaned in libsyntax Error messages cleaned in libsyntax more agressively Error messages cleaned in librustc more aggressively Fixed affected tests Fixed other failing tests Last failing tests fixed
2014-02-08	syntax: convert deriving to take &mut ExtCtxt.	Huon Wilson	-2/+2

2014-02-02	libsyntax: De-`@str` literal strings in the AST	Patrick Walton	-4/+7

2014-01-27	syntax: improve the spans of some #[deriving] traits.	Huon Wilson	-16/+20
	This makes error messages about (e.g.) `#[deriving(Clone)] struct Foo { x: Type }` point at `x: Type` rather than `Clone` in the header (while still referring to the `#[deriving(Clone)]` in the expansion info).
2014-01-09	libsyntax: Renamed types, traits and enum variants to CamelCase.	Eduard Burtescu	-4/+4

2013-12-28	Stop using @ExtCtxt	Steven Fackler	-2/+2

2013-12-07	syntax::deriving: add the cx and span to the TraitDef to reduce duplication.	Huon Wilson	-1/+3

2013-11-28	Register new snapshots	Alex Crichton	-1/+1