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

error[E0560]: struct `NonCopyable` has no field named `p`
  --> $DIR/issue-4736.rs:4:26
   |
LL | struct NonCopyable(());
   |        ----------- `NonCopyable` defined here
...
LL |     let z = NonCopyable{ p: () };
   |             -------------^------
   |             |            |
   |             |            field does not exist
   |             help: `NonCopyable` is a tuple struct, use the appropriate syntax: `NonCopyable(/* fields */)`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0560`.
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			error[E0560]: struct `NonCopyable` has no field named `p`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-4736.rs:4:26`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
provide variant definition on tuple struct unknow field error 2019-06-19 09:09:17 +00:00			`LL \| struct NonCopyable(());`
			\| ----------- `NonCopyable` defined here
			`...`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| let z = NonCopyable{ p: () };`
Fix span used for structured tuple struct suggestion (And same for tuple variants.) Previously, the span was just for the constructor name, which meant it would result in syntactically-invalid code when applied. Now, the span is for the entire expression. 2021-09-02 03:11:05 +00:00			`\| -------------^------`
			`\| \| \|`
			`\| \| field does not exist`
typeck: Emit structured suggestions for tuple struct syntax And tuple variant syntax, but that didn't fit in the subject :) Now the fact that these are suggestions is exposed both to the layout engine and to IDEs and rustfix for automatic application. 2021-02-04 05:29:00 +00:00			\| help: `NonCopyable` is a tuple struct, use the appropriate syntax: `NonCopyable(/* fields */)`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			`error: aborting due to previous error`

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