rust/tests/ui/proc-macro/derive-helper-shadowing.stderr

error: cannot use a derive helper attribute through an import
  --> $DIR/derive-helper-shadowing.rs:42:15
   |
LL |             #[renamed]
   |               ^^^^^^^
   |
note: the derive helper attribute imported here
  --> $DIR/derive-helper-shadowing.rs:41:17
   |
LL |             use empty_helper as renamed;
   |                 ^^^^^^^^^^^^^^^^^^^^^^^

error: cannot find attribute `empty_helper` in this scope
  --> $DIR/derive-helper-shadowing.rs:38:22
   |
LL |             #[derive(GenHelperUse)]
   |                      ^^^^^^^^^^^^
   |
   = note: this error originates in the derive macro `GenHelperUse` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this attribute macro through its public re-export
   |
LL +             use empty_helper;
   |

error: cannot find attribute `empty_helper` in this scope
  --> $DIR/derive-helper-shadowing.rs:14:11
   |
LL |         #[empty_helper]
   |           ^^^^^^^^^^^^
...
LL |             gen_helper_use!();
   |             ----------------- in this macro invocation
   |
   = note: this error originates in the macro `gen_helper_use` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this attribute macro through its public re-export
   |
LL +             use crate::empty_helper;
   |

error[E0659]: `empty_helper` is ambiguous
  --> $DIR/derive-helper-shadowing.rs:19:3
   |
LL | #[empty_helper]
   |   ^^^^^^^^^^^^ ambiguous name
   |
   = note: ambiguous because of a name conflict with a derive helper attribute
note: `empty_helper` could refer to the derive helper attribute defined here
  --> $DIR/derive-helper-shadowing.rs:22:10
   |
LL | #[derive(Empty)]
   |          ^^^^^
note: `empty_helper` could also refer to the attribute macro imported here
  --> $DIR/derive-helper-shadowing.rs:10:5
   |
LL | use test_macros::empty_attr as empty_helper;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   = help: use `crate::empty_helper` to refer to this attribute macro unambiguously

warning: derive helper attribute is used before it is introduced
  --> $DIR/derive-helper-shadowing.rs:19:3
   |
LL | #[empty_helper]
   |   ^^^^^^^^^^^^
...
LL | #[derive(Empty)]
   |          ----- the attribute is introduced here
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #79202 <https://github.com/rust-lang/rust/issues/79202>
   = note: `#[warn(legacy_derive_helpers)]` on by default

error: aborting due to 4 previous errors; 1 warning emitted

For more information about this error, try `rustc --explain E0659`.
Add some more tests 2019-10-05 08:59:52 -05:00			`error: cannot use a derive helper attribute through an import`
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00			`--> $DIR/derive-helper-shadowing.rs:42:15`
Add some more tests 2019-10-05 08:59:52 -05:00			`\|`
			`LL \| #[renamed]`
			`\| ^^^^^^^`
			`\|`
			`note: the derive helper attribute imported here`
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00			`--> $DIR/derive-helper-shadowing.rs:41:17`
Add some more tests 2019-10-05 08:59:52 -05:00			`\|`
			`LL \| use empty_helper as renamed;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^`

			error: cannot find attribute `empty_helper` in this scope
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00			`--> $DIR/derive-helper-shadowing.rs:38:22`
Add some more tests 2019-10-05 08:59:52 -05:00			`\|`
			`LL \| #[derive(GenHelperUse)]`
			`\| ^^^^^^^^^^^^`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06: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 13:52:25 -06:00			= note: this error originates in the derive macro `GenHelperUse` (in Nightly builds, run with -Z macro-backtrace for more info)
Tweak privacy errors to account for reachable items Suggest publicly accessible paths for items in private mod: When encountering a path in non-import situations that are not reachable due to privacy constraints, search for any public re-exports that the user could use instead. Track whether an import suggestion is offering a re-export. When encountering a path with private segments, mention if the item at the final path segment is not publicly accessible at all. Add item visibility metadata to privacy errors from imports: On unreachable imports, record the item that was being imported in order to suggest publicly available re-exports or to be explicit that the item is not available publicly from any path. In order to allow this, we add a mode to `resolve_path` that will not add new privacy errors, nor return early if it encounters one. This way we can get the `Res` corresponding to the final item in the import, which is used in the privacy error machinery. 2023-06-16 14:44:06 -05:00			`help: consider importing this attribute macro through its public re-export`
Make "consider importing" consistent for macros 2023-06-09 11:06:34 -05:00			`\|`
			`LL + use empty_helper;`
			`\|`
Add some more tests 2019-10-05 08:59:52 -05:00
			error: cannot find attribute `empty_helper` in this scope
			`--> $DIR/derive-helper-shadowing.rs:14:11`
			`\|`
			`LL \| #[empty_helper]`
			`\| ^^^^^^^^^^^^`
			`...`
			`LL \| gen_helper_use!();`
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 07:56:47 -06: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 13:52:25 -06:00			= note: this error originates in the macro `gen_helper_use` (in Nightly builds, run with -Z macro-backtrace for more info)
Tweak privacy errors to account for reachable items Suggest publicly accessible paths for items in private mod: When encountering a path in non-import situations that are not reachable due to privacy constraints, search for any public re-exports that the user could use instead. Track whether an import suggestion is offering a re-export. When encountering a path with private segments, mention if the item at the final path segment is not publicly accessible at all. Add item visibility metadata to privacy errors from imports: On unreachable imports, record the item that was being imported in order to suggest publicly available re-exports or to be explicit that the item is not available publicly from any path. In order to allow this, we add a mode to `resolve_path` that will not add new privacy errors, nor return early if it encounters one. This way we can get the `Res` corresponding to the final item in the import, which is used in the privacy error machinery. 2023-06-16 14:44:06 -05:00			`help: consider importing this attribute macro through its public re-export`
Make "consider importing" consistent for macros 2023-06-09 11:06:34 -05:00			`\|`
			`LL + use crate::empty_helper;`
			`\|`
Add some more tests 2019-10-05 08:59:52 -05:00
Edit error messages for rustc_resolve::AmbiguityKind variants Emit description of the ambiguity as a note. Co-authored-by: Noah Lev <camelidcamel@gmail.com> Co-authored-by: Vadim Petrochenkov <vadim.petrochenkov@gmail.com> 2021-10-20 08:56:10 -05:00			error[E0659]: `empty_helper` is ambiguous
Add some more tests 2019-10-05 08:59:52 -05:00			`--> $DIR/derive-helper-shadowing.rs:19:3`
resolve: Future proof derive helper attributes 2018-09-12 21:11:13 -05:00			`\|`
tests: Centralize proc macros commonly used for testing 2019-05-21 17:09:58 -05:00			`LL \| #[empty_helper]`
			`\| ^^^^^^^^^^^^ ambiguous name`
resolve: Future proof derive helper attributes 2018-09-12 21:11:13 -05:00			`\|`
Edit error messages for rustc_resolve::AmbiguityKind variants Emit description of the ambiguity as a note. Co-authored-by: Noah Lev <camelidcamel@gmail.com> Co-authored-by: Vadim Petrochenkov <vadim.petrochenkov@gmail.com> 2021-10-20 08:56:10 -05:00			`= note: ambiguous because of a name conflict with a derive helper attribute`
tests: Centralize proc macros commonly used for testing 2019-05-21 17:09:58 -05:00			note: `empty_helper` could refer to the derive helper attribute defined here
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00			`--> $DIR/derive-helper-shadowing.rs:22:10`
resolve: Future proof derive helper attributes 2018-09-12 21:11:13 -05:00			`\|`
tests: Centralize proc macros commonly used for testing 2019-05-21 17:09:58 -05:00			`LL \| #[derive(Empty)]`
			`\| ^^^^^`
			note: `empty_helper` could also refer to the attribute macro imported here
Add some more tests 2019-10-05 08:59:52 -05:00			`--> $DIR/derive-helper-shadowing.rs:10:5`
resolve: Do not block derive helper resolutions on single import resolutions Derive helpers conflict currently conflict with anything else, so if some resolution from a single import appears later, it will result in error anyway 2018-09-23 18:26:26 -05:00			`\|`
tests: Centralize proc macros commonly used for testing 2019-05-21 17:09:58 -05:00			`LL \| use test_macros::empty_attr as empty_helper;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
			= help: use `crate::empty_helper` to refer to this attribute macro unambiguously
resolve: Future proof derive helper attributes 2018-09-12 21:11:13 -05:00
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00			`warning: derive helper attribute is used before it is introduced`
			`--> $DIR/derive-helper-shadowing.rs:19:3`
			`\|`
			`LL \| #[empty_helper]`
			`\| ^^^^^^^^^^^^`
			`...`
			`LL \| #[derive(Empty)]`
			`\| ----- the attribute is introduced here`
			`\|`
			`= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!`
			`= note: for more information, see issue #79202 <https://github.com/rust-lang/rust/issues/79202>`
bless ui tests 2022-09-18 10:55:36 -05:00			= note: `#[warn(legacy_derive_helpers)]` on by default
expand/resolve: Turn `#[derive]` into a regular macro attribute 2020-11-14 05:47:14 -06:00
resolve: Remove artificial import ambiguity errors 2023-05-29 15:36:06 -05:00			`error: aborting due to 4 previous errors; 1 warning emitted`
resolve: Future proof derive helper attributes 2018-09-12 21:11:13 -05:00
resolve: Use `feature(custom_attribute)` fallback only if the feature is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros. 2019-07-11 17:00:20 -05:00			For more information about this error, try `rustc --explain E0659`.