rust/tests/ui/hygiene/impl_items.stderr

error: type `for<'a> fn(&'a foo::S) {foo::S::f}` is private
  --> $DIR/impl_items.rs:12:23
   |
LL |         let _: () = S.f();
   |                       ^ private type
...
LL |     foo::m!();
   |     --------- in this macro invocation
   |
   = note: this error originates in the macro `foo::m` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
address review 2022-09-21 17:57:30 +02:00			error: type `for<'a> fn(&'a foo::S) {foo::S::f}` is private
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/impl_items.rs:12:23`
Move hygiene tests to UI 2018-04-07 17:28:31 +03:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let _: () = S.f();`
Normalize wording of privacy access labels 2020-03-22 15:36:54 -07:00			`\| ^ private type`
Move hygiene tests to UI 2018-04-07 17:28:31 +03:00			`...`
			`LL \| foo::m!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| --------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the macro `foo::m` (in Nightly builds, run with -Z macro-backtrace for more info)
Move hygiene tests to UI 2018-04-07 17:28:31 +03:00
			`error: aborting due to previous error`