rust/tests/ui/macros/die-macro.rs

//@ run-pass
#![allow(dead_code)]
// Just testing that panic!() type checks in statement or expr


#![allow(unreachable_code)]

fn f() {
    panic!();

    let _x: isize = panic!();
}

pub fn main() {

}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 21:51:35 +00:00			`#![allow(dead_code)]`
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 19:17:22 +00:00			`// Just testing that panic!() type checks in statement or expr`
Adjust the die macro to only accept ~str and to work in statement position 2012-12-11 01:22:10 +00:00
rustdoc: Replace no-pretty-expanded with pretty-expanded 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-03-22 20:13:15 +00:00
Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 15:30:31 +00:00			`#![allow(unreachable_code)]`
Fix warnings it tests 2013-08-17 15:37:42 +00:00
Adjust the die macro to only accept ~str and to work in statement position 2012-12-11 01:22:10 +00:00			`fn f() {`
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 19:17:22 +00:00			`panic!();`
Adjust the die macro to only accept ~str and to work in statement position 2012-12-11 01:22:10 +00:00
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-26 00:06:52 +00:00			`let _x: isize = panic!();`
Adjust the die macro to only accept ~str and to work in statement position 2012-12-11 01:22:10 +00:00			`}`

check-fast fallout from removing export, r=burningtree 2013-02-02 03:43:17 +00:00			`pub fn main() {`
Adjust the die macro to only accept ~str and to work in statement position 2012-12-11 01:22:10 +00:00
			`}`