mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f4f96e2943
rust/src/test/ui/range/range-inclusive-pattern-precedence.stderr

33 lines
1.1 KiB
Plaintext
Raw Normal View History

Disallow &a..=b and box a..=b in pattern. They are disallowed because they have different precedence than expressions. I assume parenthesis in pattern will be soon stabilized and thus write that as suggestion directly.
2018-03-02 16:05:54 -06:00
error: the range pattern here has ambiguous interpretation
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/range-inclusive-pattern-precedence.rs:17:10
Disallow &a..=b and box a..=b in pattern. They are disallowed because they have different precedence than expressions. I assume parenthesis in pattern will be soon stabilized and thus write that as suggestion directly.
2018-03-02 16:05:54 -06:00
|
LL | &10..=15 => {}
| ^^^^^^^ help: add parentheses to clarify the precedence: `(10 ..=15)`
error: the range pattern here has ambiguous interpretation
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/range-inclusive-pattern-precedence.rs:28:13
Disallow &a..=b and box a..=b in pattern. They are disallowed because they have different precedence than expressions. I assume parenthesis in pattern will be soon stabilized and thus write that as suggestion directly.
2018-03-02 16:05:54 -06:00
|
LL | box 10..=15 => {}
| ^^^^^^^ help: add parentheses to clarify the precedence: `(10 ..=15)`
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/range-inclusive-pattern-precedence.rs:14: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 | &0...9 => {}
Use non-short suggestion for parenthesised ..=
2018-11-10 15:27:40 -06:00
| ^^^^^^ help: use `..=` for an inclusive range: `&(0..=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
|
note: lint level defined here
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/range-inclusive-pattern-precedence.rs:9: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)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: `...` range patterns are deprecated
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/range-inclusive-pattern-precedence.rs:25:14
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 | box 0...9 => {}
| ^^^ help: use `..=` for an inclusive range
Disallow &a..=b and box a..=b in pattern. They are disallowed because they have different precedence than expressions. I assume parenthesis in pattern will be soon stabilized and thus write that as suggestion directly.
2018-03-02 16:05:54 -06:00
error: aborting due to 2 previous errors
Reference in New Issue Copy Permalink