mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/src/test/ui/error-codes/E0423.stderr

52 lines
1.6 KiB
Text
Raw Normal View History

Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07: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 18:47:47 -07: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 17:09:03 -07: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-23 22:20:58 -07:00
|
fix typo
2019-05-02 15:53:09 -07:00
help: surround the struct literal with parentheses
Expand suggestions for type ascription parse errors
2019-03-12 19:27:10 -07:00
|
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07:00
LL | if let S { x: _x, y: 2 } = (S { x: 1, y: 2 }) { println!("Ok"); }
| ^ ^
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 18:47:47 -07:00
error: expected expression, found `==`
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07: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 18:47:47 -07:00
|
LL | if T {} == T {} { println!("Ok"); }
| ^^ expected expression
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07: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 18:47:47 -07:00
|
LL | for _ in std::ops::Range { start: 0, end: 10 } {}
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07: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-23 22:20:58 -07:00
|
fix typo
2019-05-02 15:53:09 -07:00
help: surround the struct literal with parentheses
Expand suggestions for type ascription parse errors
2019-03-12 19:27:10 -07:00
|
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07:00
LL | for _ in (std::ops::Range { start: 0, end: 10 }) {}
| ^ ^
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 18:47:47 -07:00
Move some E0XXX to `ui`
2018-02-07 19:35:35 -08:00
error[E0423]: expected function, found struct `Foo`
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/E0423.rs:4:13
Move some E0XXX to `ui`
2018-02-07 19:35:35 -08:00
|
Point at definition when misusing ADT When given `struct Foo(usize)` and using it as `Foo {}` or `Foo`, point at `Foo`'s definition in the error.
2019-09-22 11:27:55 -07:00
LL | struct Foo { a: bool };
| ---------------------- `Foo` defined here
LL |
Update tests
2019-03-09 15:03:44 +03:00
LL | let f = Foo();
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 18:47:47 -07:00
| ^^^
| |
| did you mean `Foo { /* fields */ }`?
Bring attention to suggestions when the only difference is capitalization
2019-10-13 21:48:39 -07:00
| help: a function with a similar name exists (notice the capitalization): `foo`
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 18:47:47 -07:00
error[E0423]: expected value, found struct `T`
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07:00
--> $DIR/E0423.rs:14:8
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 18:47:47 -07:00
|
LL | if T {} == T {} { println!("Ok"); }
Use structured suggestion to surround struct literal with parenthesis
2019-01-17 21:19:30 -08:00
| ^---
| |
| help: surround the struct literal with parenthesis: `(T {})`
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 18:47:47 -07:00
Emit specific error for struct literal in conditions
2019-04-14 17:09:03 -07:00
error: aborting due to 5 previous errors
Move some E0XXX to `ui`
2018-02-07 19:35:35 -08:00
update tests
2018-03-03 15:59:40 +01:00
For more information about this error, try `rustc --explain E0423`.
Reference in a new issue Copy permalink