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

Age	Commit message (Collapse)	Author	Lines
2013-05-03	add gitattributes and fix whitespace issues	Daniel Micay	-1/+0

2013-05-03	syntax: Warning police	Tim Chevalier	-3/+3

2013-05-02	librustc: Update the serializer to work properly with INHTWAMA, removing ↵	Patrick Walton	-1/+2
	mutable fields in the process
2013-05-03	More accurate spans	Seo Sanghyeon	-4/+4

2013-05-03	Use static strings	Jeong YunWon	-38/+31

2013-05-02	More cases of [cfg(test)] instead of [test].	Felix S. Klock II	-1/+1

2013-05-02	Remove 'Local Variable' comments	Brendan Zabarauskas	-49/+0

2013-05-01	syntax: fix up dynamic borrow errors in libsyntax	Niko Matsakis	-10/+10

2013-05-01	auto merge of #6148 : erickt/rust/remove-drop, r=pcwalton	bors	-164/+99
	The drop block has been deprecated for quite some time. This patch series removes support for parsing it and all the related machinery that made drop work. As a side feature of all this, I also added the ability to annote fields in structs. This allows comments to be properly associated with an individual field. However, I didn't update `rustdoc` to integrate these comment blocks into the documentation it generates.
2013-05-01	remove some warnings	Erick Tryzelaar	-1/+1

2013-05-01	syntax: remove parse::token::{dtor,literally_dtor}	Erick Tryzelaar	-75/+70

2013-05-01	allow parsing attributes on struct fields	Erick Tryzelaar	-15/+21

2013-05-01	rustc: remove the rest of drop	Erick Tryzelaar	-2/+0
	Removes: ast::struct_def::dtor syntax::ast::ii_dtor syntax::visit::fk_dtor syntax::ast_map::node_dtor syntax:struct_dtor
2013-05-01	syntax: remove parsing destructors	Erick Tryzelaar	-78/+14

2013-05-01	rustc: print out filename/line-number when a borrow fails	Niko Matsakis	-1/+1

2013-05-01	Revert rename of Div to Quot	Brendan Zabarauskas	-3/+3

2013-04-30	allover: numerous unused muts etc	Niko Matsakis	-3/+2

2013-04-29	libstd: Fix merge fallout.	Patrick Walton	-16/+14

2013-04-29	librustc: Change labels to use the lifetime notation `'`.	Patrick Walton	-20/+37

2013-04-29	librustc: Remove the concept of modes from the compiler.	Patrick Walton	-27/+35
	This commit does not remove `ty::arg`, although that should be possible to do now.
2013-04-28	parser comments	John Clements	-12/+82

2013-04-28	s/one_tuple/trailing_comma (more accurate name)	John Clements	-3/+3

2013-04-28	removed unneeded argument to parse_record	John Clements	-4/+5

2013-04-28	s/parse_purity/parse_unsafety	John Clements	-3/+4

2013-04-28	remove 3-line used-once function	John Clements	-8/+4

2013-04-28	rename parse_instance_var to parse_name_and_ty	John Clements	-3/+3
	the name no longer made sense. perhaps this could just be inlined.
2013-04-28	remove obsolete semicolon from list of suggestions	John Clements	-1/+1

2013-04-28	rename parse_single_class_item as well	John Clements	-5/+6

2013-04-28	rename parse_class_item to parse_struct_decl_field	John Clements	-3/+4
	two problems with the old name: they're not called classes any more, and the word "item" has a specific connotation in the parser
2013-04-28	needs_comma was always true	John Clements	-3/+2

2013-04-28	fix for parsing x() as identifier pattern	John Clements	-17/+14

2013-04-28	hard to read the implied double negative	John Clements	-4/+4

2013-04-28	remove unused functions, fix tiny lexing bug	John Clements	-10/+1
	before this change, the parser would parse 14.a() as a method call, but would parse 14.ø() as the floating-point number 14. followed by a function call. This is because it was checking is_alpha, rather than ident_start, and was therefore wrong with respect to unicode.
2013-04-28	remove unused flag to parse_local fn	John Clements	-5/+4

2013-04-28	remove unused RESTRICT_NO_CALL_EXPRS restriction	John Clements	-7/+2

2013-04-28	undo abstraction over whether to parse attrs in a block	John Clements	-32/+19
	In principle, it seems like a nice idea to abstract over the two functions that parse blocks (one with inner attrs allowed, one not). However, the existing one wound up making things more complex than just having two separate functions, especially after the obsolete syntax is (will be) removed.
2013-04-28	refactoring to split foreign_items from items	John Clements	-164/+169

2013-04-28	parser comments	John Clements	-6/+15
	parser comments
2013-04-28	get rid of prec.rs	John Clements	-58/+30
	prec.rs no longer had much to do with precedence; the token->binop function fits better in token.rs, and the one-liner defining the precedence of 'as' can go next to the other precedence stuff in ast_util.rs
2013-04-28	reindent in parser	John Clements	-4/+4

2013-04-28	remove unnecessary function	John Clements	-7/+1

2013-04-28	simplify, based on invariant that items_allowed != foreign_items_allowed	John Clements	-12/+7

2013-04-28	adding parse_path	John Clements	-19/+34

2013-04-28	comments, helper function for tests, more informative error message	John Clements	-2/+17

2013-04-28	refactor parse_fn_decl	John Clements	-5/+6

2013-04-28	parser comments only	John Clements	-0/+6

2013-04-28	refactoring mod.rs	John Clements	-161/+435

2013-04-27	only use #[no_core] in libcore	Daniel Micay	-31/+0

2013-04-22	auto merge of #6007 : pcwalton/rust/use-mod, r=brson	bors	-13/+8
	r? @brson
2013-04-22	auto merge of #5966 : alexcrichton/rust/issue-3083, r=graydon	bors	-19/+19
	Closes #3083. This takes a similar approach to #5797 where a set is present on the `tcx` of used mutable definitions. Everything is by default warned about, and analyses must explicitly add mutable definitions to this set so they're not warned about. Most of this was pretty straightforward, although there was one caveat that I ran into when implementing it. Apparently when the old modes are used (or maybe `legacy_modes`, I'm not sure) some different code paths are taken to cause spurious warnings to be issued which shouldn't be issued. I'm not really sure how modes even worked, so I was having a lot of trouble tracking this down. I figured that because they're a legacy thing that I'd just de-mode the compiler so that the warnings wouldn't be a problem anymore (or at least for the compiler). Other than that, the entire compiler compiles without warnings of unused mutable variables. To prevent bad warnings, #5965 should be landed (which in turn is waiting on #5963) before landing this. I figured I'd stick it out for review anyway though.