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

Age	Commit message (Collapse)	Author	Lines
2019-07-27	tests: Move run-pass tests without naming conflicts to ui	Vadim Petrochenkov	-25/+0

2019-07-27	tests: Add missing run-pass annotations	Vadim Petrochenkov	-0/+2

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-09-21	Allow various lints as part of ui-ifying `src/test/run-pass` suite.	Felix S. Klock II	-0/+1

2015-04-08	Remove pretty-expanded from failing tests	Alex Crichton	-1/+0
	This commit removes pretty-expanded from all tests that wind up calling panic! one way or another now that its internals are unstable.
2015-03-26	Mass rename uint/int to usize/isize	Alex Crichton	-4/+4
	Now that support has been removed, all lingering use cases are renamed.
2015-03-23	rustdoc: Replace no-pretty-expanded with pretty-expanded	Brian Anderson	-0/+2
	Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work.
2014-10-29	Rename fail! to panic!	Steve Klabnik	-1/+1
	https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . \| xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change]
2013-11-17	Forbid privacy in inner functions	Alex Crichton	-1/+1
	Closes #10111
2013-06-01	Remove all uses of `pub impl`. rs=style	Patrick Walton	-2/+2

2013-05-19	Use assert_eq! rather than assert! where possible	Corey Richardson	-2/+2

2013-05-03	add gitattributes and fix whitespace issues	Daniel Micay	-12/+10

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

2013-03-13	librustc: Remove implicit self from the language, except for old-style drop ↵	Patrick Walton	-1/+1
	blocks.
2013-03-07	librustc: Convert all uses of `assert` over to `fail_unless!`	Patrick Walton	-2/+2

2013-02-28	librustc: Mark all type implementations public. rs=impl-publicity	Patrick Walton	-1/+1

2013-02-13	Remove die!, raplace invocations with fail! Issue #4524 pt 3	Nick Desaulniers	-1/+1

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

2013-01-31	Replace most invocations of fail keyword with die! macro	Nick Desaulniers	-2/+2

2012-12-10	Reliciense makefiles and testsuite. Yup.	Graydon Hoare	-0/+10

2012-09-10	Convert class methods to impl methods. Stop parsing class methods	Brian Anderson	-0/+3

2012-09-07	Remove 'let' syntax for struct fields	Brian Anderson	-1/+1

2012-09-06	Remove struct ctors	Brian Anderson	-1/+6

2012-08-17	Remove the class keyword	Brian Anderson	-1/+1

2012-08-01	Convert ret to return	Brian Anderson	-1/+1

2012-06-20	Fix resolve bug that made nested classes not work	Tim Chevalier	-0/+15
	It wasn't possible to refer to the constructor for a class nested inside an item from the class's outer scope. Fixed.