rust/tests/ui/loops/issue-43162.rs

fn foo() -> bool {
    //~^ ERROR E0308
    break true; //~ ERROR E0268
}

fn main() {
    break {}; //~ ERROR E0268
}
Type-check `break value;` even outside of `loop {}`. Fix #43162, fix #43727. 2017-08-08 15:28:09 +00:00			`fn foo() -> bool {`
Fail typecheck if we encounter a bogus break Lone breaks outside of loops create errors in the loop check pass but as they are not fatal, compilation continues. MIR building code assumes all HIR break statements to point to valid locations and fires ICEs if this assumption is violated. In normal compilation, this causes no issues, as code apparently prevents MIR from being built if errors are present. However, before that, typecheck runs and with it MIR const eval. Here we operate differently from normal compilation: it doesn't check for any errors except for type checker ones and then directly builds the MIR. This constellation causes an ICE-on-error if bogus break statements are being put into array length expressions. This commit fixes this ICE by letting typecheck fail if bogus break statements are encountered. This way, MIR const eval fails cleanly with a type check error. Fixes #50576 Fixes #50581 2018-05-26 00:48:08 +00:00			`//~^ ERROR E0308`
Type-check `break value;` even outside of `loop {}`. Fix #43162, fix #43727. 2017-08-08 15:28:09 +00:00			`break true; //~ ERROR E0268`
			`}`

			`fn main() {`
			`break {}; //~ ERROR E0268`
			`}`