mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e4b9f86054
rust/tests/ui/parser/macro/macro-incomplete-parse.stderr

36 lines
1.1 KiB
Plaintext
Raw Normal View History

Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
error: macro expansion ignores token `,` and any following
fix tidy
2019-05-31 15:50:04 -05:00
--> $DIR/macro-incomplete-parse.rs:5:9
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | ,
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
| ^
Modify invalid macro in expression context diagnostic
2018-10-23 12:07:34 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | ignored_item!();
Bless tests
2021-10-14 13:28:28 -05:00
| --------------- caused by the macro expansion here
Modify invalid macro in expression context diagnostic
2018-10-23 12:07:34 -05:00
|
= note: the usage of `ignored_item!` is likely invalid in item context
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
error: expected one of `.`, `;`, `?`, `}`, or an operator, found `,`
fix tidy
2019-05-31 15:50:04 -05:00
--> $DIR/macro-incomplete-parse.rs:10:14
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | () => ( 1,
Remove "here" from "expected one of X here"
2019-10-28 13:08:53 -05:00
| ^ expected one of `.`, `;`, `?`, `}`, or an operator
Update UI test with proc_macro changes
2017-06-21 13:32:50 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | ignored_expr!();
Bless tests
2021-10-14 13:28:28 -05:00
| --------------- in this macro invocation
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.
2019-12-16 07:56:47 -06:00
|
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the macro `ignored_expr` (in Nightly builds, run with -Z macro-backtrace for more info)
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
error: macro expansion ignores token `,` and any following
fix tidy
2019-05-31 15:50:04 -05:00
--> $DIR/macro-incomplete-parse.rs:16:14
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | () => ( 1, 2 )
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
| ^
Modify invalid macro in expression context diagnostic
2018-10-23 12:07:34 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | ignored_pat!() => (),
Modify invalid macro in expression context diagnostic
2018-10-23 12:07:34 -05:00
| -------------- caused by the macro expansion here
|
= note: the usage of `ignored_pat!` is likely invalid in pattern context
Improve wording and spans for unexpected token * Point at where the token was expected instead of the last token successfuly parsed. * Only show `unexpected token` if the next char and the unexpected token don't have the same span. * Change some cfail and pfail tests to ui test. * Don't show all possible tokens in span label if they are more than 6.
2017-03-25 17:36:59 -05:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-07-02 05:49:30 -05:00
error: aborting due to 3 previous errors
Fix unittests
2017-03-25 21:06:19 -05:00
Reference in New Issue Copy Permalink