rust/src/test/ui/impossible_range.stderr

error[E0586]: inclusive range with no end
  --> $DIR/impossible_range.rs:20:8
   |
20 |     ..=; //~ERROR inclusive range with no end
   |        ^
   |
   = help: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)

error[E0586]: inclusive range with no end
  --> $DIR/impossible_range.rs:27:9
   |
27 |     0..=; //~ERROR inclusive range with no end
   |         ^
   |
   = help: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)

error: aborting due to 2 previous errors
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`error[E0586]: inclusive range with no end`
Do not emit type errors on recovered blocks When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. 2017-12-14 01:05:49 -06:00			`--> $DIR/impossible_range.rs:20:8`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Do not emit type errors on recovered blocks When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. 2017-12-14 01:05:49 -06:00			`20 \| ..=; //~ERROR inclusive range with no end`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\| ^`
			`\|`
			= help: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)

			`error[E0586]: inclusive range with no end`
Do not emit type errors on recovered blocks When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. 2017-12-14 01:05:49 -06:00			`--> $DIR/impossible_range.rs:27:9`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Do not emit type errors on recovered blocks When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. 2017-12-14 01:05:49 -06:00			`27 \| 0..=; //~ERROR inclusive range with no end`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\| ^`
			`\|`
			= help: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)

			`error: aborting due to 2 previous errors`