rust/tests/ui/macros/issue-78325-inconsistent-resolution.stderr

error: macro-expanded `extern crate` items cannot shadow names passed with `--extern`
  --> $DIR/issue-78325-inconsistent-resolution.rs:3:9
   |
LL |         extern crate std as core;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^
...
LL | define_other_core!();
   | -------------------- in this macro invocation
   |
   = note: this error originates in the macro `define_other_core` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
resolve: Relax macro resolution consistency check to account for any errors 2020-10-24 21:17:34 +03:00			error: macro-expanded `extern crate` items cannot shadow names passed with `--extern`
			`--> $DIR/issue-78325-inconsistent-resolution.rs:3:9`
			`\|`
			`LL \| extern crate std as core;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^`
			`...`
			`LL \| define_other_core!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| -------------------- in this macro invocation`
resolve: Relax macro resolution consistency check to account for any errors 2020-10-24 21:17:34 +03: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 `define_other_core` (in Nightly builds, run with -Z macro-backtrace for more info)
resolve: Relax macro resolution consistency check to account for any errors 2020-10-24 21:17:34 +03:00
			`error: aborting due to previous error`