rust/tests/ui/issues/issue-2150.rs

#![deny(unreachable_code)]
#![allow(unused_variables)]
#![allow(dead_code)]

fn fail_len(v: Vec<isize> ) -> usize {
    let mut i = 3;
    panic!();
    for x in &v { i += 1; }
    //~^ ERROR: unreachable statement
    return i;
}
fn main() {}
Convert most code to new inner attribute syntax. Closes #2569 2014-03-21 18:05:05 -07:00			`#![deny(unreachable_code)]`
Update code with new lint names 2014-10-27 15:37:07 -07:00			`#![allow(unused_variables)]`
Convert most code to new inner attribute syntax. Closes #2569 2014-03-21 18:05:05 -07:00			`#![allow(dead_code)]`
test: Make manual changes to deal with the fallout from removal of `~[T]` in test, libgetopts, compiletest, librustdoc, and libnum. 2014-03-05 15:28:08 -08:00
Update compile fail tests to use usize. 2015-01-08 22:02:42 +11:00			`fn fail_len(v: Vec<isize> ) -> usize {`
Promote unreachable code to being a lint attribute 2013-05-30 03:03:32 -05:00			`let mut i = 3;`
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!();`
Remove integer suffixes where the types in compiled code are identical. 2015-03-03 10:42:26 +02:00			`for x in &v { i += 1; }`
Promote unreachable code to being a lint attribute 2013-05-30 03:03:32 -05:00			`//~^ ERROR: unreachable statement`
Convert ret to return 2012-08-01 17:30:05 -07:00			`return i;`
Do not consider ty_bot to be a "resolved type". Fixes #2149. Fixes #2150. Fixes #2151. 2012-04-07 17:11:33 -07:00			`}`
Replace most invocations of fail keyword with die! macro 2013-01-31 17:51:01 -08:00			`fn main() {}`