os-rust/tests/ui/error-codes/E0423.stderr

error: struct literals are not allowed here
  --> $DIR/E0423.rs:12:32
   |
LL |     if let S { x: _x, y: 2 } = S { x: 1, y: 2 } { println!("Ok"); }
   |                                ^^^^^^^^^^^^^^^^
   |
help: surround the struct literal with parentheses
   |
LL |     if let S { x: _x, y: 2 } = (S { x: 1, y: 2 }) { println!("Ok"); }
   |                                +                +

error: expected expression, found `==`
  --> $DIR/E0423.rs:14:13
   |
LL |     if T {} == T {} { println!("Ok"); }
   |             ^^ expected expression

error: struct literals are not allowed here
  --> $DIR/E0423.rs:20:14
   |
LL |     for _ in std::ops::Range { start: 0, end: 10 } {}
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
help: surround the struct literal with parentheses
   |
LL |     for _ in (std::ops::Range { start: 0, end: 10 }) {}
   |              +                                     +

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"); }
   |        +    +

error[E0423]: expected function, tuple struct or tuple variant, found struct `Foo`
  --> $DIR/E0423.rs:4:13
   |
LL |     struct Foo { a: bool };
   |     ---------------------- `Foo` defined here
LL |
LL |     let f = Foo();
   |             ^^^^^
...
LL | fn foo() {
   | -------- similarly named function `foo` defined here
   |
help: use struct literal syntax instead
   |
LL |     let f = Foo { a: val };
   |             ~~~~~~~~~~~~~~
help: a function with a similar name exists (notice the capitalization difference)
   |
LL |     let f = foo();
   |             ~~~

error: aborting due to 5 previous errors

For more information about this error, try `rustc --explain E0423`.
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"); }`
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 19:07:19 -07: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 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 }) {}`
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 19:07:19 -07: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 18:47:47 -07:00
Delay function resolution error until typeck 2022-10-05 05:35:34 +00: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 17:20:50 -07:00			error[E0423]: expected function, tuple struct or tuple variant, 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			`\|`
Bless tests 2020-03-21 15:03:58 +01:00			`LL \| struct Foo { a: bool };`
			\| ---------------------- `Foo` defined here
fix one more case of trailing space 2022-06-08 21:07:59 +03:00			`LL \|`
Bless tests 2020-03-21 15:03:58 +01: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 17:42:07 -07:00			`\| ^^^^^`
Tweak ordering of suggestions Modify logic to make it easier to follow and recover labels that would otherwise be lost. 2020-08-09 20:29:39 -07: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 17:42:07 -07: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 19:07:19 -07:00			`\| ~~~~~~~~~~~~~~`
Fix msg for verbose suggestions with confusable capitalization When encountering a verbose/multipart suggestion that has changes that are only caused by different capitalization of ASCII letters that have little differenciation, expand the message to highlight that fact (like we already do for inline suggestions). The logic to do this was already present, but implemented incorrectly. 2024-02-14 19:18:28 +00:00			`help: a function with a similar name exists (notice the capitalization difference)`
Tweak ordering of suggestions Modify logic to make it easier to follow and recover labels that would otherwise be lost. 2020-08-09 20:29:39 -07:00			`\|`
			`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 19:07:19 -07: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 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`.