rust/tests/ui/imports/extern-prelude-extern-crate-restricted-shadowing.stderr

error: macro-expanded `extern crate` items cannot shadow names passed with `--extern`
  --> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:19: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[E0659]: `Vec` is ambiguous
  --> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:13:9
   |
LL |         Vec::panic!();
   |         ^^^ ambiguous name
   |
   = note: ambiguous because of a conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution
note: `Vec` could refer to the crate imported here
  --> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:5:9
   |
LL |         extern crate std as Vec;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^
...
LL | define_vec!();
   | ------------- in this macro invocation
note: `Vec` could also refer to a struct from prelude
  --> $SRC_DIR/std/src/prelude/mod.rs:LL:COL
   = note: this error originates in the macro `define_vec` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0659`.
Add a couple more tests 2018-11-20 16:28:07 -06:00			error: macro-expanded `extern crate` items cannot shadow names passed with `--extern`
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-03-31 20:10:13 -05:00			`--> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:19:9`
Add a couple more tests 2018-11-20 16:28:07 -06:00			`\|`
			`LL \| extern crate std as core;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^`
			`...`
			`LL \| define_other_core!();`
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 `define_other_core` (in Nightly builds, run with -Z macro-backtrace for more info)
Add a couple more tests 2018-11-20 16:28:07 -06: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]: `Vec` is ambiguous
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-03-31 20:10:13 -05:00			`--> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:13:9`
Add `extern crate` items to extern prelude 2018-09-28 17:31:54 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| Vec::panic!();`
Add `extern crate` items to extern prelude 2018-09-28 17:31:54 -05:00			`\| ^^^ ambiguous name`
			`\|`
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 conflict between a macro-expanded name and a less macro-expanded name from outer scope during import or macro resolution`
Point at local similarly named element and tweak references to variants Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method. 2019-10-14 19:20:50 -05:00			note: `Vec` could refer to the crate imported here
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-03-31 20:10:13 -05:00			`--> $DIR/extern-prelude-extern-crate-restricted-shadowing.rs:5:9`
Add `extern crate` items to extern prelude 2018-09-28 17:31:54 -05:00			`\|`
			`LL \| extern crate std as Vec;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^`
			`...`
			`LL \| define_vec!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ------------- in this macro invocation`
Make some diagnostics not depend on the source of what they reference being available 2022-12-09 09:56:23 -06:00			note: `Vec` could also refer to a struct from prelude
Update test output for edition preludes. 2021-02-17 08:52:31 -06:00			`--> $SRC_DIR/std/src/prelude/mod.rs:LL:COL`
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 `define_vec` (in Nightly builds, run with -Z macro-backtrace for more info)
Add `extern crate` items to extern prelude 2018-09-28 17:31:54 -05:00
Add a couple more tests 2018-11-20 16:28:07 -06:00			`error: aborting due to 2 previous errors`
Add `extern crate` items to extern prelude 2018-09-28 17:31:54 -05:00
			For more information about this error, try `rustc --explain E0659`.