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

Age	Commit message (Collapse)	Author	Lines
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	-2/+2

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

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/+68

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	-4/+5

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 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/+8
	parser comments
2013-04-28	get rid of prec.rs	John Clements	-3/+2
	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	-1/+11

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

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

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

2013-04-27	only use #[no_core] in libcore	Daniel Micay	-2/+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	-14/+14
	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.
2013-04-22	librustc: Remove `use mod` from the language	Patrick Walton	-13/+8

2013-04-22	Rename Div operator trait to Quot and Modulo operator trait to Rem	Brendan Zabarauskas	-2/+2

2013-04-20	syntax: remove unused 'mut' variables	Alex Crichton	-14/+14

2013-04-19	syntax: de-mode and prepare for de-modeing rustc	Alex Crichton	-30/+30

2013-04-16	add self.token_to_str and is_any_keyword convenience abstractions	John Clements	-17/+28

2013-04-16	added MTWT functions	John Clements	-1/+1

2013-04-16	better error message on failure to parse type	John Clements	-1/+2

2013-04-10	libsyntax comments only	John Clements	-17/+42

2013-04-10	unneccessary since tjc's commit 78ec6fe30cf2b, fixing #2804	John Clements	-4/+0

2013-04-10	path -> Path	John Clements	-8/+8

2013-04-05	Refactor so that references to traits are not represented using a type with a	Niko Matsakis	-17/+8
	bare function store (which is not in fact a kind of value) but rather ty::TraitRef. Removes many uses of fail!() and other telltale signs of type-semantic mismatch. cc #4183 (not a fix, but related)
2013-04-03	auto merge of #5696 : thestinger/rust/hashmap, r=sanxiyn	bors	-6/+6
	This naming is free now that `oldmap` has finally been removed, so this is a search-and-replace to take advantage of that. It might as well be called `HashMap` instead of being named after the specific implementation, since there's only one. SipHash distributes keys so well that I don't think there will ever be much need to use anything but a simple hash table with open addressing. If there is a better way to do it, it will probably be better in all cases and can just be the default implementation. A cuckoo-hashing implementation combining a weaker hash with SipHash could be useful, but that won't be as general purpose - you would need to write a separate fast hash function specialized for the type to really take advantage of it (like taking a page from libstdc++/libc++ and just using the integer value as the "hash"). I think a more specific naming for a truly alternative implementation like that would be fine, with the nice naming reserved for the general purpose container.
2013-04-03	auto merge of #5559 : jbclements/rust/change-to-tt-based-parsing, r=jbclements	bors	-0/+24
	Changes the parser to parse all streams into token-trees before hitting the parser proper, in preparation for hygiene. As an added bonus, it appears to speed up the parser (albeit by a totally imperceptible 1%). Also, many comments in the parser. Also, field renaming in token-trees (readme->forest, cur->stack).
2013-04-03	rename Linear{Map,Set} => Hash{Map,Set}	Daniel Micay	-6/+6

2013-04-03	hashmap: rm linear namespace	Daniel Micay	-1/+1

2013-03-31	Fix warnings	Brian Anderson	-1/+1