about summary refs log tree commit diff
path: root/src/test/run-fail/fail-main.rs
AgeCommit message (Collapse)AuthorLines
2014-11-11test: Rename files, fail -> panic.Michael Sproul-12/+0
2014-10-29Rename 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-03-14extra: Put the nail in the coffin, delete libextraAlex Crichton-1/+0
This commit shreds all remnants of libextra from the compiler and standard distribution. Two modules, c_vec/tempfile, were moved into libstd after some cleanup, and the other modules were moved to separate crates as seen fit. Closes #8784 Closes #12413 Closes #12576
2014-02-14extern mod => extern crateAlex Crichton-1/+1
This was previously implemented, and it just needed a snapshot to go through
2013-10-22Drop the '2' suffix from logging macrosAlex Crichton-1/+1
Who doesn't like a massive renaming?
2013-09-30rfail: Remove usage of fmt!Alex Crichton-1/+1
2013-05-22test: Update tests to use the new syntax.Patrick Walton-1/+1
2013-05-14Use static string with fail!() and remove fail!(fmt!())Björn Steinbrink-1/+1
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-13Remove die!, raplace invocations with fail! Issue #4524 pt 3Nick Desaulniers-1/+1
2013-01-31Replace most invocations of fail keyword with die! macroNick Desaulniers-1/+1
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-09-11Convert 'use' to 'extern mod'. Remove old 'use' syntaxBrian Anderson-1/+1
2012-09-05test: "import" -> "use"Patrick Walton-1/+0
2012-07-14Move the world over to using the new style string literals and types. Closes ↵Michael Sullivan-1/+1
#2907.
2011-12-13Copy first batch of material from libstd to libcore.Graydon Hoare-1/+1
2011-08-20ReformatBrian 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-03Remove all xfail-stage0 directivesBrian 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-27Reformat for new syntaxMarijn Haverbeke-3/+1
2011-07-05Handle fail inside a for-each loop properlyTim Chevalier-0/+7