Zack M. Davis c2d44b2286 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:48:05 -07:00
..
issue-33174-restricted-type-in-public-interface.rs	in which the private/restricted-in-public error messaging gets specific	2018-06-30 22:48:05 -07:00
issue-33174-restricted-type-in-public-interface.stderr	in which the private/restricted-in-public error messaging gets specific	2018-06-30 22:48:05 -07:00
pub-restricted-error-fn.rs	Merge cfail and ui tests into ui tests	2017-11-24 11:32:35 +01:00
pub-restricted-error-fn.stderr	Update UI tests	2018-02-26 20:24:02 +03:00
pub-restricted-error.rs	Auto merge of #45997 - estebank:pub-ident, r=nikomatsakis	2017-12-01 06:06:06 +00:00
pub-restricted-error.stderr	Update UI tests	2018-02-26 20:24:02 +03:00
pub-restricted-non-path.rs	Merge cfail and ui tests into ui tests	2017-11-24 11:32:35 +01:00
pub-restricted-non-path.stderr	Update UI tests	2018-02-26 20:24:02 +03:00
pub-restricted.rs	Merge cfail and ui tests into ui tests	2017-11-24 11:32:35 +01:00
pub-restricted.stderr	Update error code numbers	2018-06-19 17:33:14 -07:00