mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2d45df3caa
rust/tests/ui/range/range-inclusive-pattern-precedence.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
916 B
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
Fix tests
2021-04-16 04:06:51 -05:00
--> $DIR/range-inclusive-pattern-precedence.rs:15: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 => {}
Fix whitespace in pretty printed PatKind::Range
2021-12-29 14:51:10 -06:00
| ^^^^^^^ help: add parentheses to clarify the precedence: `(10..=15)`
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
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
Audit uses of `span_suggestion_short`
2020-07-02 00:32:12 -05:00
--> $DIR/range-inclusive-pattern-precedence.rs:11: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
|
bless ui tests
2022-09-18 10:55:36 -05:00
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/warnings-promoted-to-error.html>
Normalise notes with the/is
2020-01-22 17:57:38 -06:00
note: the lint level is defined here
Audit uses of `span_suggestion_short`
2020-07-02 00:32:12 -05:00
--> $DIR/range-inclusive-pattern-precedence.rs:7: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)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Audit uses of `span_suggestion_short`
2020-07-02 00:32:12 -05:00
error: aborting due to previous error; 1 warning emitted
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
Reference in New Issue Copy Permalink