rust/src/test/ui/issues/issue-63983.stderr

error[E0532]: expected unit struct, unit variant or constant, found tuple variant `MyEnum::Tuple`
  --> $DIR/issue-63983.rs:8:9
   |
LL |     Tuple(i32),
   |     ---------- `MyEnum::Tuple` defined here
...
LL |         MyEnum::Tuple => "",
   |         ^^^^^^^^^^^^^ help: use the tuple variant pattern syntax instead: `MyEnum::Tuple(_)`

error[E0532]: expected unit struct, unit variant or constant, found struct variant `MyEnum::Struct`
  --> $DIR/issue-63983.rs:10:9
   |
LL |     Struct{ s: i32 },
   |     ---------------- `MyEnum::Struct` defined here
...
LL |         MyEnum::Struct => "",
   |         ^^^^^^^^^^^^^^ help: use struct pattern syntax instead: `MyEnum::Struct { s }`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0532`.
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[E0532]: expected unit struct, unit variant or constant, found tuple variant `MyEnum::Tuple`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00			`--> $DIR/issue-63983.rs:8:9`
			`\|`
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 13:27:55 -05:00			`LL \| Tuple(i32),`
			\| ---------- `MyEnum::Tuple` defined here
			`...`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00			`LL \| MyEnum::Tuple => "",`
Detect tuple variants used as struct pattern and suggest correct pattern 2020-08-09 19:52:29 -05:00			\| ^^^^^^^^^^^^^ help: use the tuple variant pattern syntax instead: `MyEnum::Tuple(_)`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00
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[E0532]: expected unit struct, unit variant or constant, found struct variant `MyEnum::Struct`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00			`--> $DIR/issue-63983.rs:10:9`
			`\|`
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 13:27:55 -05:00			`LL \| Struct{ s: i32 },`
			\| ---------------- `MyEnum::Struct` defined here
			`...`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00			`LL \| MyEnum::Struct => "",`
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 pattern syntax instead: `MyEnum::Struct { s }`
unify errors for tuple/struct variants fix #63983 2019-09-21 10:36:12 -05:00
			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0532`.