nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-01 06:51:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
e78e747f53
rust/src/test/ui/parser/expr-as-stmt.stderr

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

217 lines
5.1 KiB
Plaintext
Raw Normal View History

Use verbose suggestions and only match if the + is seen before a numeric literal
2021-09-05 02:35:59 +00:00
error: expected expression, found `+`
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:8:9
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | {2} + {2}
Use verbose suggestions and only match if the + is seen before a numeric literal
2021-09-05 02:35:59 +00:00
| ^ expected expression
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-06-28 18:22:47 +00:00
|
help: parentheses are required to parse this as an expression
|
LL | ({2}) + {2}
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| + +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
Add checks for a block before a unary plus. Fix failing tests
2021-09-01 15:54:06 +00:00
error: leading `+` is not supported
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:13:9
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | {2} + 2
Add checks for a block before a unary plus. Fix failing tests
2021-09-01 15:54:06 +00:00
| ^ unexpected `+`
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-06-28 18:22:47 +00:00
|
help: parentheses are required to parse this as an expression
|
LL | ({2}) + 2
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| + +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
Use verbose suggestions and only match if the + is seen before a numeric literal
2021-09-05 02:35:59 +00:00
error: expected expression, found `+`
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:19:12
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | { 42 } + foo;
Use verbose suggestions and only match if the + is seen before a numeric literal
2021-09-05 02:35:59 +00:00
| ^ expected expression
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-06-28 18:22:47 +00:00
|
help: parentheses are required to parse this as an expression
|
LL | ({ 42 }) + foo;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| + +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
Reword ambigous parse error to fit with the current error
2019-05-01 03:37:42 +00:00
error: expected expression, found `>`
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:32:7
Add test case for #47287
2019-04-29 21:35:09 +00:00
|
LL | } > 0
Reword ambigous parse error to fit with the current error
2019-05-01 03:37:42 +00:00
| ^ expected expression
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-24 05:20:58 +00:00
|
fix typo
2019-05-02 22:53:09 +00:00
help: parentheses are required to parse this as an expression
Add test case for #47287
2019-04-29 21:35:09 +00:00
|
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
LL ~ (match x {
Add test case for #47287
2019-04-29 21:35:09 +00:00
LL | _ => 1,
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
LL ~ }) > 0
Add test case for #47287
2019-04-29 21:35:09 +00:00
|
diagnostic: suggest parens when users want logical ops, but get closures
2022-02-25 00:02:38 +00:00
error: expected parameter name, found `{`
--> $DIR/expr-as-stmt.rs:41:16
|
LL | { true } | { true }
| ^ expected parameter name
|
help: parentheses are required to parse this as an expression
|
LL | ({ true }) | { true }
| + +
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:64:7
|
LL | { foo() } || { true }
| ^^^^^- help: consider using a semicolon here: `;`
| |
| expected `()`, found `i32`
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
error[E0308]: mismatched types
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:8:6
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | {2} + {2}
Surround types with backticks in type errors
2019-11-15 17:37:01 +00:00
| ^ expected `()`, found integer
Suggest `return`ing tail expressions that match return type Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2021-02-04 20:22:01 +00:00
|
help: you might have meant to return this value
|
LL | {return 2;} + {2}
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ++++++ +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
error[E0308]: mismatched types
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:13:6
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | {2} + 2
Surround types with backticks in type errors
2019-11-15 17:37:01 +00:00
| ^ expected `()`, found integer
Suggest `return`ing tail expressions that match return type Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2021-02-04 20:22:01 +00:00
|
help: you might have meant to return this value
|
LL | {return 2;} + 2
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ++++++ +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
error[E0308]: mismatched types
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:19:7
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | { 42 } + foo;
Surround types with backticks in type errors
2019-11-15 17:37:01 +00:00
| ^^ expected `()`, found integer
Suggest `return`ing tail expressions that match return type Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2021-02-04 20:22:01 +00:00
|
help: you might have meant to return this value
|
LL | { return 42; } + foo;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ++++++ +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
error[E0308]: mismatched types
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:25:7
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | { 3 } * 3
Surround types with backticks in type errors
2019-11-15 17:37:01 +00:00
| ^ expected `()`, found integer
Suggest `return`ing tail expressions that match return type Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2021-02-04 20:22:01 +00:00
|
help: you might have meant to return this value
|
LL | { return 3; } * 3
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| ++++++ +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
error[E0614]: type `{integer}` cannot be dereferenced
Update rustfix for compiletest.
2021-06-11 03:39:05 +00:00
--> $DIR/expr-as-stmt.rs:25:11
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
|
LL | { 3 } * 3
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-06-28 18:22:47 +00:00
| ^^^
|
help: parentheses are required to parse this as an expression
|
LL | ({ 3 }) * 3
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-22 02:07:19 +00:00
| + +
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
Suggest wapping expr in parentheses on invalid unary negation Fixes #88701
2021-09-06 22:30:20 +00:00
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:36:6
|
LL | {2} - 2
| ^ expected `()`, found integer
|
help: you might have meant to return this value
|
LL | {return 2;} - 2
| ++++++ +
error[E0600]: cannot apply unary operator `-` to type `u32`
--> $DIR/expr-as-stmt.rs:36:9
|
LL | {2} - 2
| ^^^ cannot apply unary operator `-`
|
help: parentheses are required to parse this as an expression
|
LL | ({2}) - 2
| + +
diagnostic: suggest parens when users want logical ops, but get closures
2022-02-25 00:02:38 +00:00
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:41:7
|
LL | { true } | { true }
| ^^^^ expected `()`, found `bool`
|
help: you might have meant to return this value
|
LL | { return true; } | { true }
| ++++++ +
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:46:7
|
LL | { true } && { true }
| ^^^^ expected `()`, found `bool`
|
help: you might have meant to return this value
|
LL | { return true; } && { true }
| ++++++ +
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:46:14
|
LL | fn revenge_from_mars() -> bool {
| ---- expected `bool` because of return type
LL | { true } && { true }
| ^^^^^^^^^^^ expected `bool`, found `&&bool`
|
Make deref suggestion better
2021-12-05 04:51:36 +00:00
help: consider removing the `&&`
|
LL - { true } && { true }
LL + { true } { true }
diagnostics: fix trailing space
2022-06-08 17:34:57 +00:00
|
diagnostic: suggest parens when users want logical ops, but get closures
2022-02-25 00:02:38 +00:00
help: parentheses are required to parse this as an expression
|
LL | ({ true }) && { true }
| + +
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:51:7
|
LL | { true } || { true }
| ^^^^ expected `()`, found `bool`
|
help: you might have meant to return this value
|
LL | { return true; } || { true }
| ++++++ +
error[E0308]: mismatched types
--> $DIR/expr-as-stmt.rs:51:14
|
LL | fn attack_from_mars() -> bool {
| ---- expected `bool` because of return type
LL | { true } || { true }
| ^^^^^^^^^^^ expected `bool`, found closure
|
= note: expected type `bool`
found closure `[closure@$DIR/expr-as-stmt.rs:51:14: 51:25]`
Improve suggestion for calling closure on type mismatch
2022-06-20 06:11:31 +00:00
help: use parentheses to call this closure
|
LL | { true } (|| { true })()
| + +++
diagnostic: suggest parens when users want logical ops, but get closures
2022-02-25 00:02:38 +00:00
help: parentheses are required to parse this as an expression
|
LL | ({ true }) || { true }
| + +
error: aborting due to 18 previous errors
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
Suggest wapping expr in parentheses on invalid unary negation Fixes #88701
2021-09-06 22:30:20 +00:00
Some errors have detailed explanations: E0308, E0600, E0614.
Identify when a stmt could have been parsed as an expr There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.
2019-04-23 02:37:23 +00:00
For more information about an error, try `rustc --explain E0308`.
Reference in New Issue Copy Permalink