rust/tests/ui/parser/struct-literal-restrictions-in-lamda.stderr

error: struct literals are not allowed here
  --> $DIR/struct-literal-restrictions-in-lamda.rs:12:14
   |
LL |       while || Foo {
   |  ______________^
LL | |         x: 3
LL | |     }.hi() {
   | |_____^
   |
help: surround the struct literal with parentheses
   |
LL ~     while || (Foo {
LL |         x: 3
LL ~     }).hi() {
   |

error[E0308]: mismatched types
  --> $DIR/struct-literal-restrictions-in-lamda.rs:12:11
   |
LL |       while || Foo {
   |  ___________^
LL | |         x: 3
LL | |     }.hi() {
   | |__________^ expected `bool`, found closure
   |
   = note: expected type `bool`
           found closure `{closure@$DIR/struct-literal-restrictions-in-lamda.rs:12:11: 12:13}`
help: use parentheses to call this closure
   |
LL ~     while (|| Foo {
LL |         x: 3
LL ~     }.hi())() {
   |

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0308`.
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			`error: struct literals are not allowed here`
			`--> $DIR/struct-literal-restrictions-in-lamda.rs:12:14`
Expand suggestions for type ascription parse errors 2019-03-13 02:27:10 +00:00			`\|`
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			`LL \| while \|\| Foo {`
			`\| ______________^`
			`LL \| \| x: 3`
			`LL \| \| }.hi() {`
			`\| \|_____^`
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: surround the struct literal with parentheses`
Expand suggestions for type ascription parse errors 2019-03-13 02:27:10 +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 ~ while \|\| (Foo {`
Expand suggestions for type ascription parse errors 2019-03-13 02:27:10 +00:00			`LL \| x: 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			`LL ~ }).hi() {`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00			`\|`

Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			`error[E0308]: mismatched types`
			`--> $DIR/struct-literal-restrictions-in-lamda.rs:12:11`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 15:33:05 +00:00			`\|`
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			`LL \| while \|\| Foo {`
			`\| ___________^`
			`LL \| \| x: 3`
			`LL \| \| }.hi() {`
Surround types with backticks in type errors 2019-11-15 17:37:01 +00:00			\| \|__________^ expected `bool`, found closure
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 15:33:05 +00:00			`\|`
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			= note: expected type `bool`
adjust how closure/generator types and rvalues are printed 2023-09-09 06:36:50 +00:00			found closure `{closure@$DIR/struct-literal-restrictions-in-lamda.rs:12:11: 12:13}`
Improve suggestion for calling closure on type mismatch 2022-06-20 06:11:31 +00:00			`help: use parentheses to call this closure`
			`\|`
			`LL ~ while (\|\| Foo {`
			`LL \| x: 3`
			`LL ~ }.hi())() {`
			`\|`
tests: Do not use `-Z parse-only`, continue compilation to test recovery 2019-01-06 15:33:05 +00:00
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			`error: aborting due to 2 previous errors`
Move parse-fail tests to UI 2018-10-20 20:36:17 +00:00
Emit specific error for struct literal in conditions 2019-04-15 00:09:03 +00:00			For more information about this error, try `rustc --explain E0308`.