rust/tests/ui/issues/issue-32086.stderr

error[E0532]: expected tuple struct or tuple variant, found constant `C`
  --> $DIR/issue-32086.rs:5:9
   |
LL | struct S(u8);
   | ------------- similarly named tuple struct `S` defined here
...
LL |     let C(a) = S(11);
   |         ^ help: a tuple struct with a similar name exists: `S`

error[E0532]: expected tuple struct or tuple variant, found constant `C`
  --> $DIR/issue-32086.rs:6:9
   |
LL | struct S(u8);
   | ------------- similarly named tuple struct `S` defined here
...
LL |     let C(..) = S(11);
   |         ^ help: a tuple struct with a similar name exists: `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 tuple struct or tuple variant, found constant `C`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-32086.rs:5:9`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -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			`LL \| struct S(u8);`
			\| ------------- similarly named tuple struct `S` defined here
			`...`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| let C(a) = S(11);`
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion. 2019-01-09 13:11:00 -06:00			\| ^ help: a tuple struct with a similar name exists: `S`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -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 tuple struct or tuple variant, found constant `C`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-32086.rs:6:9`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -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			`LL \| struct S(u8);`
			\| ------------- similarly named tuple struct `S` defined here
			`...`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| let C(..) = S(11);`
clarify resolve typo suggestion Include the kind of the binding that we're suggesting, and use a structured suggestion. 2019-01-09 13:11:00 -06:00			\| ^ help: a tuple struct with a similar name exists: `S`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to 2 previous errors`

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