rust/src/test/ui/lint/inclusive-range-pattern-syntax.stderr

warning: `...` range patterns are deprecated
  --> $DIR/inclusive-range-pattern-syntax.rs:9:10
   |
LL |         1...2 => {}
   |          ^^^ help: use `..=` for an inclusive range
   |
note: lint level defined here
  --> $DIR/inclusive-range-pattern-syntax.rs:4:9
   |
LL | #![warn(ellipsis_inclusive_range_patterns)]
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: `...` range patterns are deprecated
  --> $DIR/inclusive-range-pattern-syntax.rs:15:9
   |
LL |         &1...2 => {}
   |         ^^^^^^ help: use `..=` for an inclusive range: `&(1..=2)`
inclusive range syntax lint (`...` → `..=`) Our implementation ends up changing the `PatKind::Range` variant in the AST to take a `Spanned<RangeEnd>` instead of just a `RangeEnd`, because the alternative would be to try to infer the span of the range operator from the spans of the start and end subexpressions, which is both hideous and nontrivial to get right (whereas getting the change to the AST right was a simple game of type tennis). This is concerning #51043. 2018-05-28 21:32:03 -05:00			warning: `...` range patterns are deprecated
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/inclusive-range-pattern-syntax.rs:9:10`
inclusive range syntax lint (`...` → `..=`) Our implementation ends up changing the `PatKind::Range` variant in the AST to take a `Spanned<RangeEnd>` instead of just a `RangeEnd`, because the alternative would be to try to infer the span of the range operator from the spans of the start and end subexpressions, which is both hideous and nontrivial to get right (whereas getting the change to the AST right was a simple game of type tennis). This is concerning #51043. 2018-05-28 21:32:03 -05:00			`\|`
			`LL \| 1...2 => {}`
			\| ^^^ help: use `..=` for an inclusive range
			`\|`
			`note: lint level defined here`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/inclusive-range-pattern-syntax.rs:4:9`
inclusive range syntax lint (`...` → `..=`) Our implementation ends up changing the `PatKind::Range` variant in the AST to take a `Spanned<RangeEnd>` instead of just a `RangeEnd`, because the alternative would be to try to infer the span of the range operator from the spans of the start and end subexpressions, which is both hideous and nontrivial to get right (whereas getting the change to the AST right was a simple game of type tennis). This is concerning #51043. 2018-05-28 21:32:03 -05:00			`\|`
			`LL \| #![warn(ellipsis_inclusive_range_patterns)]`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint 2018-11-10 12:08:50 -06:00			warning: `...` range patterns are deprecated
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/inclusive-range-pattern-syntax.rs:15:9`
Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint 2018-11-10 12:08:50 -06:00			`\|`
			`LL \| &1...2 => {}`
Use non-short suggestion for parenthesised ..= 2018-11-10 15:27:40 -06:00			\| ^^^^^^ help: use `..=` for an inclusive range: `&(1..=2)`
Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint 2018-11-10 12:08:50 -06:00