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

Age	Commit message (Collapse)	Author	Lines
2014-11-11	test: Rename files, fail -> panic.	Michael Sproul	-16/+0

2014-10-29	Rename fail! to panic!	Steve Klabnik	-2/+2
	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-02	tests: remove uses of Gc.	Eduard Burtescu	-4/+2

2014-07-26	Remove managed_box gate from tests	Brian Anderson	-1/+0
	No longer does anything.
2014-06-14	rustc: Obsolete the `@` syntax entirely	Alex Crichton	-2/+5
	This removes all remnants of `@` pointers from rustc. Additionally, this removes the `GC` structure from the prelude as it seems odd exporting an experimental type in the prelude by default. Closes #14193 [breaking-change]
2014-04-14	Use new attribute syntax in python files in src/etc too (#13478)	Manish Goregaokar	-1/+1

2013-10-23	register snapshots	Daniel Micay	-0/+2

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

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

2013-05-14	Use static string with fail!() and remove fail!(fmt!())	Björn Steinbrink	-2/+2
	fail!() used to require owned strings but can handle static strings now. Also, it can pass its arguments to fmt!() on its own, no need for the caller to call fmt!() itself.
2013-02-13	Remove die!, raplace invocations with fail! Issue #4524 pt 3	Nick Desaulniers	-2/+2

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-07-14	Move the world over to using the new style string literals and types. Closes ↵	Michael Sullivan	-2/+2
	#2907.
2011-08-20	Reformat	Brian Anderson	-1/+1
	This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-03	Remove all xfail-stage0 directives	Brian Anderson	-1/+0
	While it is still technically possible to test stage 0, it is not part of any of the main testing rules and maintaining xfail-stage0 is a chore. Nobody should worry about how tests fare in stage0.
2011-07-27	Reformat for new syntax	Marijn Haverbeke	-6/+2

2011-07-03	Handle fail as an argument; parse fail expressions unambiguously	Tim Chevalier	-0/+9
	An expression like: foo(1, fail, 2) was failing to parse, because the parser was interpreting the comma as the start of an expression that was an argument to fail, rather than recognizing that the fail here has no arguments Fixed this by using can_begin_expr to determine whether the next token after a fail token suggests that this is a nullary fail or a unary fail. In addition, when translating calls, check before translating each argument that the block still isn't terminated. This has the effect that if an argument list includes fail, the back-end won't keep trying to generate code for successive arguments and trip the !*terminated assertion.