rust/tests/ui/parser/range_inclusive.stderr

error[E0586]: inclusive range with no end
  --> $DIR/range_inclusive.rs:5:15
   |
LL |     for _ in 1..= {}
   |               ^^^
   |
   = note: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)
help: use `..` instead
   |
LL -     for _ in 1..= {}
LL +     for _ in 1.. {}
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0586`.
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`error[E0586]: inclusive range with no end`
Audit uses of `span_suggestion_short` 2020-07-02 05:32:12 +00:00			`--> $DIR/range_inclusive.rs:5:15`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| for _ in 1..= {}`
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			`\| ^^^`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`
Ban `...X` pats, harden tests, and improve diagnostics. Also fix a bug with the span passed in `mk_range`. 2020-01-11 05:49:43 +00:00			= note: inclusive ranges must be bounded at the end (`..=b` or `a..=b`)
Make parse error suggestions verbose and fix spans Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts. 2024-07-06 03:07:46 +00:00			help: use `..` instead
			`\|`
			`LL - for _ in 1..= {}`
			`LL + for _ in 1.. {}`
			`\|`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
			For more information about this error, try `rustc --explain E0586`.