mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a11805ae46
rust/tests/ui/error-codes/E0423.stderr

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

64 lines
1.8 KiB
Plaintext
Raw Normal View History

Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
error: struct literals are not allowed here
--> $DIR/E0423.rs:12:32
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
|
LL | if let S { x: _x, y: 2 } = S { x: 1, y: 2 } { println!("Ok"); }
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
| ^^^^^^^^^^^^^^^^
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 00:20:58 -05:00
|
fix typo
2019-05-02 17:53:09 -05:00
help: surround the struct literal with parentheses
Expand suggestions for type ascription parse errors
2019-03-12 21:27:10 -05:00
|
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
LL | if let S { x: _x, y: 2 } = (S { x: 1, y: 2 }) { println!("Ok"); }
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-21 21:07:19 -05:00
| + +
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
error: expected expression, found `==`
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
--> $DIR/E0423.rs:14:13
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
|
LL | if T {} == T {} { println!("Ok"); }
| ^^ expected expression
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
error: struct literals are not allowed here
--> $DIR/E0423.rs:20:14
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
|
LL | for _ in std::ops::Range { start: 0, end: 10 } {}
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 00:20:58 -05:00
|
fix typo
2019-05-02 17:53:09 -05:00
help: surround the struct literal with parentheses
Expand suggestions for type ascription parse errors
2019-03-12 21:27:10 -05:00
|
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
LL | for _ in (std::ops::Range { start: 0, end: 10 }) {}
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-21 21:07:19 -05:00
| + +
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
Delay function resolution error until typeck
2022-10-05 00:35:34 -05:00
error[E0423]: expected value, found struct `T`
--> $DIR/E0423.rs:14:8
|
LL | if T {} == T {} { println!("Ok"); }
| ^ not a value
|
help: surround the struct literal with parentheses
|
LL | if (T {}) == T {} { println!("Ok"); }
| + +
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-14 19:20:50 -05:00
error[E0423]: expected function, tuple struct or tuple variant, found struct `Foo`
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/E0423.rs:4:13
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
|
Bless tests
2020-03-21 09:03:58 -05:00
LL | struct Foo { a: bool };
| ---------------------- `Foo` defined here
fix one more case of trailing space
2022-06-08 13:07:59 -05:00
LL |
Bless tests
2020-03-21 09:03:58 -05:00
LL | let f = Foo();
Suggest struct pat on incorrect unit or tuple pat When encountering a unit or tuple pattern for a struct-like item, suggest using the correct pattern. Use `insert_field_names_local` when evaluating variants and store field names even when the list is empty in order to produce accurate structured suggestions.
2020-07-09 19:42:07 -05:00
| ^^^^^
Tweak ordering of suggestions Modify logic to make it easier to follow and recover labels that would otherwise be lost.
2020-08-09 22:29:39 -05:00
...
LL | fn foo() {
| -------- similarly named function `foo` defined here
Suggest struct pat on incorrect unit or tuple pat When encountering a unit or tuple pattern for a struct-like item, suggest using the correct pattern. Use `insert_field_names_local` when evaluating variants and store field names even when the list is empty in order to produce accurate structured suggestions.
2020-07-09 19:42:07 -05:00
|
help: use struct literal syntax instead
|
LL | let f = Foo { a: val };
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-21 21:07:19 -05:00
| ~~~~~~~~~~~~~~
Tweak ordering of suggestions Modify logic to make it easier to follow and recover labels that would otherwise be lost.
2020-08-09 22:29:39 -05:00
help: a function with a similar name exists
|
LL | let f = 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-21 21:07:19 -05:00
| ~~~
Suggest braces when a struct literal needs them When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-06-04 20:47:47 -05:00
Emit specific error for struct literal in conditions
2019-04-14 19:09:03 -05:00
error: aborting due to 5 previous errors
Move some E0XXX to `ui`
2018-02-07 21:35:35 -06:00
update tests
2018-03-03 08:59:40 -06:00
For more information about this error, try `rustc --explain E0423`.
Reference in New Issue Copy Permalink