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

Age	Commit message (Collapse)	Author	Lines
2013-08-01	std: Change `Times` trait to use `do` instead of `for`	blake2-ppc	-1/+1
	Change the former repetition:: for 5.times { } to:: do 5.times { } .times() cannot be broken with `break` or `return` anymore; for those cases, use a numerical range loop instead.
2013-05-19	Use assert_eq! rather than assert! where possible	Corey Richardson	-13/+13

2013-03-29	librustc: Remove `fail_unless!`	Patrick Walton	-13/+13

2013-03-07	test: Fix tests.	Patrick Walton	-0/+2

2013-03-07	librustc: Convert all uses of `assert` over to `fail_unless!`	Patrick Walton	-13/+13

2013-02-01	check-fast fallout from removing export, r=burningtree	Graydon Hoare	-1/+1

2013-01-30	rustc: make integral type inference transactional, close #3211, close #4401, ↵	Graydon Hoare	-11/+2
	close #3398.
2012-12-10	Reliciense makefiles and testsuite. Yup.	Graydon Hoare	-0/+10

2012-09-25	Demode Num trait and impls	Tim Chevalier	-10/+10

2012-07-10	Get rid of places that expected foo.bar to implicitly bind.	Michael Sullivan	-10/+10

2012-07-05	A new `times` method on numeric types	Ben Striegel	-2/+15
	This method is intended to elegantly subsume two common iteration functions. The first is `iter::range`, which is used identically to the method introduced in this commit, but currently works only on uints. The second is a common case of `{int, i8, uint, etc.}::range`, in the case where the inductive variable is ignored. Compare the usage of the three: ``` for iter::range(100u) { // do whatever } for int::range(0, 100) \|_i\| { // do whatever } for 100.times { // do whatever } ``` I feel that the latter reads much more nicely than the first two approaches, and unlike the first two the new method allows the user to ignore the specific type of the number (ineed, if we're throwing away the inductive variable, who cares what type it is?). A minor benefit is that this new method will be somewhat familiar to users of Ruby, from which we borrow the name "times".
2012-06-25	Remove redundant 'extension' mods from numeric mods	Brian Anderson	-3/+5

2012-06-25	Automatically export methods on core numeric types	Ben Striegel	-0/+24
	Each numeric type now contains an extensions module that is automatically exported. At the moment each extensions module contains only the impl for the `num::num` iface. Other impls soon to follow (hopefully).