mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a733082be9
rust/tests/ui/lint/inclusive-range-pattern-syntax.stderr

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

26 lines
1.0 KiB
Plaintext
Raw Normal View History

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
|
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
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
Fix tests
2021-04-16 04:06:51 -05:00
--> $DIR/inclusive-range-pattern-syntax.rs:16: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)`
Fix tests
2021-04-16 04:06:51 -05:00
|
Address PR feedback
2021-06-16 07:27:44 -05:00
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
Link to edition guide instead of issues for 2021 lints.
2021-08-09 10:45:01 -05:00
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/warnings-promoted-to-error.html>
Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint
2018-11-10 12:08:50 -06:00
rustc: Add a warning count upon completion
2020-03-11 10:30:09 -05:00
warning: 2 warnings emitted
Reference in New Issue Copy Permalink