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	-28/+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-13	Ensure that attributes are spelled properly.	Ahmed Charles	-2/+2

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.
2015-01-30	Remove all `i` suffixes	Tobias Bucher	-1/+1

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-10-28	Update tests with the new error messages	Jakub Bukaj	-2/+0

2014-06-29	librustc: Remove the fallback to `int` for integers and `f64` for	Patrick Walton	-2/+2
	floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change]
2014-04-14	Use new attribute syntax in python files in src/etc too (#13478)	Manish Goregaokar	-3/+3

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

2013-03-11	Remove uses of log	Brian Anderson	-8/+0

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

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-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-09-07	Convert 'again' to 'loop'. Remove 'again' keyword	Brian Anderson	-1/+1

2012-08-06	Convert alt to match. Stop parsing alt	Brian Anderson	-1/+1

2012-08-05	Switch alts to use arrows	Brian Anderson	-2/+2

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

2012-07-26	Re-added test for Issue 935 -- not sure what happened to it	Tim Chevalier	-0/+31

2012-04-30	Stop inferring bot/static when types/regions are unconstrained.	Niko Matsakis	-57/+0
	Also, some other changes that came up along the way: - add a 'blk' region for the current block. - detect unused type/region variables.
2012-04-07	Do not consider ty_bot to be a "resolved type".	Niko Matsakis	-4/+1
	Fixes #2149. Fixes #2150. Fixes #2151.
2012-03-26	Disallow ret inside of block functions	Marijn Haverbeke	-1/+1
	Also adds proper checking for cont/break being inside a loop. Closes #1854 Issue #1619
2012-03-24	Avoid unifying vars when possible; handle bot (more) correctly	Niko Matsakis	-2/+2

2012-03-22	make --enforce-mut-vars always on, add mut annotations to remaining files	Niko Matsakis	-1/+1

2012-03-09	Add an infinite loop construct	Tim Chevalier	-1/+1
	Add a loop {} construct for infinite loops, and use it in test cases. See #1906 for details.
2012-02-15	Rewrite exhaustiveness checker	Marijn Haverbeke	-1/+1
	Issue #352 Closes #1720 The old checker would happily accept things like 'alt x { @some(a) { a } }'. It now properly descends into patterns, checks exhaustiveness of booleans, and complains when number/string patterns aren't exhaustive.
2012-01-09	Change all uses of 'when' in alt-patterns to 'if'	Austin Seipp	-1/+1
	Issue #1396
2011-12-22	Register new snapshots, purge log_err and log_full in favour of log(...).	Graydon Hoare	-4/+4

2011-12-22	Register snapshots and switch logging over to use of log_full or #error / ↵	Graydon Hoare	-4/+4
	#debug.
2011-10-21	Remove remaining uses of iter and for-each	Marijn Haverbeke	-4/+0
	Issue #1056
2011-09-27	Test for #924	Jesse Ruderman	-1/+16

2011-09-25	Test for #973	Jesse Ruderman	-0/+4

2011-09-25	Test for #942	Jesse Ruderman	-0/+2

2011-09-23	Add more unreachable-code tests. Closes #935	Jesse Ruderman	-0/+6

2011-09-23	xfail-pretty unreachable-code.rs	Marijn Haverbeke	-0/+2

2011-09-23	Better handling of unreachable code in trans	Marijn Haverbeke	-0/+35
	The builder functions in trans_build now look at an 'unreachable' flag in the block context and don't generate code (returning undefined placeholder values) when this flag is set. Threading the unreachable flag through context still requires some care, but this seems a more sane approach than re-checking for terminated blocks throughout the compiler. When creating a block, if you use its closest dominator as parent, the flag will be automatically passed through. If you can't do that, because the dominator is a scope block that you're trying to get out of, you'll have to do something like this to explicitly pass on the flag: if bcx.unreachable { Unreachable(next_cx); } Closes #949. Closes #946. Closes #942. Closes #895. Closes #894. Closes #892. Closes #957. Closes #958.