rust/src/test/ui/span/borrowck-ref-into-rvalue.rs

fn main() {
    let msg;
    match Some("Hello".to_string()) {
        Some(ref m) => {
        //~^ ERROR borrowed value does not live long enough
            msg = m;
        },
        None => { panic!() }
    }
    println!("{}", *msg);
}
forgotten tests for #3217, #2977, #3067 2012-08-17 19:30:29 -05:00			`fn main() {`
			`let msg;`
std: Remove String's to_owned 2014-05-25 05:10:11 -05:00			`match Some("Hello".to_string()) {`
Merge cfail and ui tests into ui tests 2017-11-20 06:13:27 -06:00			`Some(ref m) => {`
Point at var in short lived borrows 2017-12-13 19:27:23 -06:00			`//~^ ERROR borrowed value does not live long enough`
forgotten tests for #3217, #2977, #3067 2012-08-17 19:30:29 -05:00			`msg = m;`
new borrow checker (mass squash) 2013-03-15 14:24:24 -05:00			`},`
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			`None => { panic!() }`
Point at var in short lived borrows 2017-12-13 19:27:23 -06:00			`}`
Remove re-exports of std::io::stdio::{print, println} in the prelude. The `print!` and `println!` macros are now the preferred method of printing, and so there is no reason to export the `stdio` functions in the prelude. The functions have also been replaced by their macro counterparts in the tutorial and other documentation so that newcomers don't get confused about what they should be using. 2014-01-09 04:06:55 -06:00			`println!("{}", *msg);`
forgotten tests for #3217, #2977, #3067 2012-08-17 19:30:29 -05:00			`}`