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	-19/+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/+2

2016-08-22	Fix compiletest so it respects warnings for run-pass.	Ahmed Charles	-2/+2

2016-08-13	Ensure that attributes are spelled properly.	Ahmed Charles	-1/+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-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]
2014-04-14	Use new attribute syntax in python files in src/etc too (#13478)	Manish Goregaokar	-2/+2

2013-10-22	Drop the '2' suffix from logging macros	Alex Crichton	-1/+1
	Who doesn't like a massive renaming?
2013-09-30	rpass: Remove usage of fmt!	Alex Crichton	-1/+1

2013-08-17	Fix warnings it tests	Erick Tryzelaar	-0/+2

2013-02-15	tests/tutorials: Get rid of `move`.	Luqman Aden	-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	-1/+1

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

2012-10-30	Remove xfail-pretty from tests that pretty-print correctly now	Tim Chevalier	-1/+0

2012-10-23	Remove uses of binary move - <- - from tests and libraries	Tim Chevalier	-1/+1

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

2012-06-30	change the test suite `//! kind` syntax to `//~ kind` in order to avoid a	Gareth Daniel Smith	-1/+1
	conflict with the new single-line-sugared-inner-doc-comment (`//! ...`).
2012-04-30	Stop inferring bot/static when types/regions are unconstrained.	Niko Matsakis	-0/+13
	Also, some other changes that came up along the way: - add a 'blk' region for the current block. - detect unused type/region variables.