rust/tests/ui/borrowck/borrowck-vec-pattern-tail-element-loan.rs

fn a<'a>() -> &'a isize {
    let vec = vec![1, 2, 3, 4];
    let vec: &[isize] = &vec;
    let tail = match vec {
        &[_a, ref tail @ ..] => &tail[0],
        _ => panic!("foo")
    };
    tail //~ ERROR cannot return value referencing local variable `vec`
}

fn main() {
    let fifth = a();
    println!("{}", *fifth);
}
Update compile fail tests to use isize. 2015-01-08 21:54:35 +11:00			`fn a<'a>() -> &'a isize {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 22:54:04 +01:00			`let vec = vec![1, 2, 3, 4];`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`let vec: &[isize] = &vec;`
new borrow checker (mass squash) 2013-03-15 15:24:24 -04:00			`let tail = match vec {`
Use new 'p @ ..' syntax in tests. 2019-07-08 01:47:46 +02:00			`&[_a, ref tail @ ..] => &tail[0],`
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 15:17:22 -04:00			`_ => panic!("foo")`
Add more tests 2012-12-15 23:13:55 +00:00			`};`
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			tail //~ ERROR cannot return value referencing local variable `vec`
Add more tests 2012-12-15 23:13:55 +00:00			`}`

			`fn main() {`
			`let fifth = a();`
Update the compiler to not use printf/printfln 2013-09-24 22:16:43 -07:00			`println!("{}", *fifth);`
Add more tests 2012-12-15 23:13:55 +00:00			`}`