rust/tests/ui/loops/unreachable-while-loop-5741.rs

// https://github.com/rust-lang/rust/issues/5741
//@ run-pass
#![allow(while_true)]
#![allow(unreachable_code)]

pub fn main() {
    return;
    while true {};
}
Add test batch 1 2025-08-20 14:02:39 -04:00			`// https://github.com/rust-lang/rust/issues/5741`
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 14:18:55 +02:00			`//@ run-pass`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 15:02:01 +02:00			`#![allow(while_true)]`
Use new attribute syntax in python files in src/etc too (#13478) 2014-04-14 21:00:31 +05:30			`#![allow(unreachable_code)]`
Fix warnings it tests 2013-08-17 08:37:42 -07:00
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 00:43:37 -07:00			`pub fn main() {`
rustc: Don't generate code for unreachable expressions The way we deal with unreachable expressions in trans is pretty ad hoc, but this at least doesn't make it worse, and eliminates the LLVM assertion failure reported in #5741. 2013-05-21 13:15:48 -07:00			`return;`
Remove even more of std::io Big fish fried here: extra::json most of the compiler extra::io_util removed extra::fileinput removed Fish left to fry extra::ebml 2013-10-13 18:48:47 -07:00			`while true {};`
rustc: Don't generate code for unreachable expressions The way we deal with unreachable expressions in trans is pretty ad hoc, but this at least doesn't make it worse, and eliminates the LLVM assertion failure reported in #5741. 2013-05-21 13:15:48 -07:00			`}`