os-rust/src/test/ui/loops/loop-break-value-no-repeat.stderr

error[E0571]: `break` with value from a `for` loop
  --> $DIR/loop-break-value-no-repeat.rs:22:9
   |
LL |         break 22 //~ ERROR `break` with value from a `for` loop
   |         ^^^^^^^^ can only break with a value inside `loop` or breakable block
help: instead, use `break` on its own without a value inside this `for` loop
   |
LL |         break //~ ERROR `break` with value from a `for` loop
   |         ^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0571`.
rework how we handle the type of loops First, we keep a `CoerceMany` now to find the LUB of all the break expressions. Second, this `CoerceMany` is actually an `Option<CoerceMany>`, and we store `None` for loops where "break with an expression" is disallowed. This avoids silly duplicate errors about a type mismatch, since the loops pass already reports an error that the break cannot have an expression. Finally, since we now detect an invalid break target during HIR lowering, refactor `find_loop` to be infallible. Adjust tests as needed: - some spans from breaks are slightly different - break up a single loop into multiple since `CoerceMany` silences redundant and derived errors - add a ui test that we only give on error for loop-break-value 2017-03-17 11:49:53 -04:00			error[E0571]: `break` with value from a `for` loop
Stabilize the loop_break_value feature 2017-05-15 22:11:16 +02:00			`--> $DIR/loop-break-value-no-repeat.rs:22:9`
rework how we handle the type of loops First, we keep a `CoerceMany` now to find the LUB of all the break expressions. Second, this `CoerceMany` is actually an `Option<CoerceMany>`, and we store `None` for loops where "break with an expression" is disallowed. This avoids silly duplicate errors about a type mismatch, since the loops pass already reports an error that the break cannot have an expression. Finally, since we now detect an invalid break target during HIR lowering, refactor `find_loop` to be infallible. Adjust tests as needed: - some spans from breaks are slightly different - break up a single loop into multiple since `CoerceMany` silences redundant and derived errors - add a ui test that we only give on error for loop-break-value 2017-03-17 11:49:53 -04:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			LL \| break 22 //~ ERROR `break` with value from a `for` loop
Make the compiler support the label-break-value feature No error checking or feature gating yet 2018-04-25 19:28:04 +02:00			\| ^^^^^^^^ can only break with a value inside `loop` or breakable block
Suggest removing value from `break` when invalid 2018-01-28 11:14:09 -08:00			help: instead, use `break` on its own without a value inside this `for` loop
			`\|`
Update UI tests 2018-02-25 02:01:39 +03:00			LL \| break //~ ERROR `break` with value from a `for` loop
Suggest removing value from `break` when invalid 2018-01-28 11:14:09 -08:00			`\| ^^^^^`
rework how we handle the type of loops First, we keep a `CoerceMany` now to find the LUB of all the break expressions. Second, this `CoerceMany` is actually an `Option<CoerceMany>`, and we store `None` for loops where "break with an expression" is disallowed. This avoids silly duplicate errors about a type mismatch, since the loops pass already reports an error that the break cannot have an expression. Finally, since we now detect an invalid break target during HIR lowering, refactor `find_loop` to be infallible. Adjust tests as needed: - some spans from breaks are slightly different - break up a single loop into multiple since `CoerceMany` silences redundant and derived errors - add a ui test that we only give on error for loop-break-value 2017-03-17 11:49:53 -04:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. 2017-07-02 13:49:30 +03:00			`error: aborting due to previous error`
rework how we handle the type of loops First, we keep a `CoerceMany` now to find the LUB of all the break expressions. Second, this `CoerceMany` is actually an `Option<CoerceMany>`, and we store `None` for loops where "break with an expression" is disallowed. This avoids silly duplicate errors about a type mismatch, since the loops pass already reports an error that the break cannot have an expression. Finally, since we now detect an invalid break target during HIR lowering, refactor `find_loop` to be infallible. Adjust tests as needed: - some spans from breaks are slightly different - break up a single loop into multiple since `CoerceMany` silences redundant and derived errors - add a ui test that we only give on error for loop-break-value 2017-03-17 11:49:53 -04:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0571`.