rust/tests/ui/unreachable-code-1.rs

//@ run-pass

#![allow(unused_must_use)]
#![allow(unreachable_code)]

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

fn id(x: bool) -> bool { x }

fn call_id() {
    let c = panic!();
    id(c);
}

fn call_id_3() { id(return) && id(return); }

pub fn main() {
}
tests: Add missing run-pass annotations 2019-07-26 21:54:25 +00:00			`//@ run-pass`

Allow various lints as part of ui-ifying `src/test/run-pass` suite. 2018-09-14 10:20:28 +00:00			`#![allow(unused_must_use)]`
			`#![allow(unreachable_code)]`
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
Ensure that attributes are spelled properly. 2016-08-13 09:41:43 +00:00			`#![allow(unused_variables)]`
Fix compiletest so it respects warnings for run-pass. 2016-08-22 23:51:37 +00:00			`#![allow(dead_code)]`
Do not consider ty_bot to be a "resolved type". Fixes #2149. Fixes #2150. Fixes #2151. 2012-04-08 00:11:33 +00:00
			`fn id(x: bool) -> bool { x }`

			`fn call_id() {`
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			`let c = panic!();`
Fix compiletest so it respects warnings for run-pass. 2016-08-22 23:51:37 +00:00			`id(c);`
Do not consider ty_bot to be a "resolved type". Fixes #2149. Fixes #2150. Fixes #2151. 2012-04-08 00:11:33 +00:00			`}`

Convert ret to return 2012-08-02 00:30:05 +00:00			`fn call_id_3() { id(return) && id(return); }`
Do not consider ty_bot to be a "resolved type". Fixes #2149. Fixes #2150. Fixes #2151. 2012-04-08 00:11:33 +00:00
check-fast fallout from removing export, r=burningtree 2013-02-02 03:43:17 +00:00			`pub fn main() {`
Do not consider ty_bot to be a "resolved type". Fixes #2149. Fixes #2150. Fixes #2151. 2012-04-08 00:11:33 +00:00			`}`