about summary refs log tree commit diff
path: root/src/test/run-fail/unwind-interleaved.rs
AgeCommit message (Collapse)AuthorLines
2020-05-06Move tests from `test/run-fail` to UIYuki Okushi-14/+0
2018-12-25Remove licensesMark Rousskov-10/+0
2016-06-06run rustfmt on test/run-fail folderSrinivas Reddy Thatiparthy-4/+6
2015-01-30Remove all `i` suffixesTobias Bucher-2/+2
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-06-29librustc: Remove the fallback to `int` for integers and `f64` forPatrick 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-03-21test: Automatically remove all `~[T]` from tests.Patrick Walton-2/+2
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-08-17Fix warnings it testsErick Tryzelaar-2/+2
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-2/+2
2012-12-10Reliciense makefiles and testsuite. Yup.Graydon Hoare-0/+10
2012-06-29Switch the compiler over to using ~[] notation instead of []/~. Closes #2759.Michael Sullivan-2/+2
2012-06-25Make vectors uglier ([]/~). Sorry. Should be temporary. Closes #2725.Michael Sullivan-2/+2
2011-09-14Add another unwind testBrian Anderson-0/+12
This makes sure that cleanups added after the first invoke in a scope are actually run on unwind