rust/tests/ui/panic-runtime/unwind-rec2.rs

//@ run-fail
//@ error-pattern:explicit panic
//@ needs-subprocess

fn build1() -> Vec<isize> {
    vec![0, 0, 0, 0, 0, 0, 0]
}

fn build2() -> Vec<isize> {
    panic!();
}

struct Blk {
    node: Vec<isize>,
    span: Vec<isize>,
}

fn main() {
    let _blk = Blk {
        node: build1(),
        span: build2(),
    };
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-fail`
			`//@ error-pattern:explicit panic`
tests: use `needs-subprocess` instead of `ignore-{wasm32,emscripten,sgx}` 2025-01-23 08:36:54 +00:00			`//@ needs-subprocess`
test: Make manual changes to deal with the fallout from removal of `~[T]` in test, libgetopts, compiletest, librustdoc, and libnum. 2014-03-05 23:28:08 +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			`fn build1() -> Vec<isize> {`
run rustfmt on test/run-fail folder 2016-05-27 02:39:36 +00:00			`vec![0, 0, 0, 0, 0, 0, 0]`
Build records in two phases to avoid cleanups on partial records 2011-09-19 21:20:15 +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			`fn build2() -> Vec<isize> {`
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!();`
Build records in two phases to avoid cleanups on partial records 2011-09-19 21:20:15 +00:00			`}`

run rustfmt on test/run-fail folder 2016-05-27 02:39:36 +00:00			`struct Blk {`
			`node: Vec<isize>,`
			`span: Vec<isize>,`
			`}`
testsuite: Eliminate structural records from run-fail tests 2013-01-26 08:25:41 +00:00
Build records in two phases to avoid cleanups on partial records 2011-09-19 21:20:15 +00:00			`fn main() {`
Fix warnings it tests 2013-08-17 15:37:42 +00:00			`let _blk = Blk {`
Build records in two phases to avoid cleanups on partial records 2011-09-19 21:20:15 +00:00			`node: build1(),`
run rustfmt on test/run-fail folder 2016-05-27 02:39:36 +00:00			`span: build2(),`
Build records in two phases to avoid cleanups on partial records 2011-09-19 21:20:15 +00:00			`};`
Replace most invocations of fail keyword with die! macro 2013-02-01 01:51:01 +00:00			`}`