rust/src/test/ui/error-codes/E0446.stderr

error[E0446]: private type `Foo::Bar` in public interface
  --> $DIR/E0446.rs:14:5
   |
LL |       struct Bar(u32);
   |       - `Foo::Bar` declared as private
LL | 
LL | /     pub fn bar() -> Bar { //~ ERROR E0446
LL | |         Bar(0)
LL | |     }
   | |_____^ can't leak private type

error: aborting due to previous error

For more information about this error, try `rustc --explain E0446`.
Move some E0XXX to `ui` 2018-02-07 19:35:35 -08:00			error[E0446]: private type `Foo::Bar` in public interface
			`--> $DIR/E0446.rs:14:5`
			`\|`
in which the private/restricted-in-public error messaging gets specific April 2016's Issue #33174 called out the E0446 diagnostics as confusing. While adding the name of the restricted type to the message (548e681f) clarified matters somewhat, Esteban Küber pointed out that we could stand to place a secondary span on the restricted type. Here, we differentiate between crate-visible, truly private, and otherwise restricted types, and place a secondary span specifically on the visibility modifier of the restricted type's declaration (which we can do now that HIR visibilities have spans!). At long last, this resolves #33174. 2018-06-30 22:08:27 -07:00			`LL \| struct Bar(u32);`
			\| - `Foo::Bar` declared as private
			`LL \|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| / pub fn bar() -> Bar { //~ ERROR E0446`
			`LL \| \| Bar(0)`
			`LL \| \| }`
Move some E0XXX to `ui` 2018-02-07 19:35:35 -08:00			`\| \|_____^ can't leak private type`

			`error: aborting due to previous error`

update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0446`.