rust/src/test/ui/panics/doublepanic.rs

#![allow(unreachable_code)]

// run-fail
// error-pattern:One

fn main() {
    panic!("One");
    panic!("Two");
}
Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 10:30:31 -05:00			`#![allow(unreachable_code)]`
Fix warnings it tests 2013-08-17 10:37:42 -05:00
Move tests from `test/run-fail` to UI 2020-04-16 01:50:32 -05:00			`// run-fail`
run rustfmt on test/run-fail folder 2016-05-26 21:39:36 -05:00			`// error-pattern:One`
Move tests from `test/run-fail` to UI 2020-04-16 01:50:32 -05:00
Fix ICE stemming from use of unique pointers in unreachable blocks. 2012-10-21 02:42:53 -05:00			`fn main() {`
Rename fail! to panic! 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-09 14:17:22 -05:00			`panic!("One");`
			`panic!("Two");`
Replace most invocations of fail keyword with die! macro 2013-01-31 19:51:01 -06:00			`}`