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

// run-pass
#![allow(unused_must_use)]
// pretty-expanded FIXME #23616

#![allow(unreachable_code)]

fn foo() -> bool { false }

fn bar() {
    return;
    !foo();
}

fn baz() {
    return;
    if "" == "" {}
}

pub fn main() {
    bar();
    baz();
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 12:18:55 +00:00			`// run-pass`
Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling with clean stderr again. Most were added mechanically. 2018-09-25 21:51:35 +00:00			`#![allow(unused_must_use)]`
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			`// pretty-expanded FIXME #23616`

Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 15:30:31 +00:00			`#![allow(unreachable_code)]`
rustc: handle allocas and LoadRangeAsserts in unreachable blocks correctly. An alloca in an unreachable block would shortcircuit with Undef, but with type `Type`, rather than type `*Type` (i.e. a plain value, not a pointer) but it is expected to return a pointer into the stack, leading to confusion and LLVM asserts later. Similarly, attaching the range metadata to a Load in an unreachable block makes LLVM unhappy, since the Load returns Undef. Fixes #7344. 2013-07-17 08:13:23 +00:00
			`fn foo() -> bool { false }`

			`fn bar() {`
			`return;`
			`!foo();`
			`}`

			`fn baz() {`
			`return;`
			`if "" == "" {}`
			`}`

Fix run-pass tests to have 'pub fn main' This is required by the check-fast target because each test is slurped up into a submodule. 2013-09-25 07:43:37 +00:00			`pub fn main() {`
rustc: handle allocas and LoadRangeAsserts in unreachable blocks correctly. An alloca in an unreachable block would shortcircuit with Undef, but with type `Type`, rather than type `*Type` (i.e. a plain value, not a pointer) but it is expected to return a pointer into the stack, leading to confusion and LLVM asserts later. Similarly, attaching the range metadata to a Load in an unreachable block makes LLVM unhappy, since the Load returns Undef. Fixes #7344. 2013-07-17 08:13:23 +00:00			`bar();`
			`baz();`
			`}`