rust/tests/ui/imports/issue-53269.stderr

error[E0432]: unresolved import `nonexistent_module`
  --> $DIR/issue-53269.rs:6:9
   |
LL |     use nonexistent_module::mac;
   |         ^^^^^^^^^^^^^^^^^^ you might be missing crate `nonexistent_module`
   |
help: consider importing the `nonexistent_module` crate
   |
LL + extern crate nonexistent_module;
   |

error[E0659]: `mac` is ambiguous
  --> $DIR/issue-53269.rs:8:5
   |
LL |     mac!();
   |     ^^^ ambiguous name
   |
   = note: ambiguous because of a conflict between a `macro_rules` name and a non-`macro_rules` name from another module
note: `mac` could refer to the macro defined here
  --> $DIR/issue-53269.rs:3:1
   |
LL | macro_rules! mac { () => () }
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: `mac` could also refer to the unresolved item imported here
  --> $DIR/issue-53269.rs:6:9
   |
LL |     use nonexistent_module::mac;
   |         ^^^^^^^^^^^^^^^^^^^^^^^
   = help: use `self::mac` to refer to this unresolved item unambiguously

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0432, E0659.
For more information about an error, try `rustc --explain E0432`.
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			error[E0432]: unresolved import `nonexistent_module`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-53269.rs:6:9`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| use nonexistent_module::mac;`
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 \| LL \| use spam::*; \| ^^^^ you might be missing crate `spam` \| = help: consider adding `extern crate spam` to use the `spam` crate ``` 2024-07-23 19:43:46 +00:00			\| ^^^^^^^^^^^^^^^^^^ you might be missing crate `nonexistent_module`
suggest `extern crate foo` when failing to resolve `use foo` fix ci error 2022-05-22 02:48:35 +00:00			`\|`
Structured suggestion for `extern crate foo` when `foo` isn't resolved in import When encountering a name in an import that could have come from a crate that wasn't imported, use a structured suggestion to suggest `extern crate foo;` pointing at the right place in the crate. When encountering `_` in an import, do not suggest `extern crate _;`. ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 \| LL \| use spam::*; \| ^^^^ maybe a missing crate `spam`? \| help: consider importing the `spam` crate \| LL + extern crate spam; \| ``` 2024-07-24 19:31:02 +00:00			help: consider importing the `nonexistent_module` crate
			`\|`
			`LL + extern crate nonexistent_module;`
			`\|`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00: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 13:56:10 +00:00			error[E0659]: `mac` is ambiguous
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-53269.rs:8:5`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| mac!();`
resolve: More precise spans for ambiguous resolution errors Add labels to ambiguous resolution errors 2018-09-07 23:51:20 +00:00			`\| ^^^ ambiguous name`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00: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 13:56:10 +00:00			= note: ambiguous because of a conflict between a `macro_rules` name and a non-`macro_rules` name from another module
resolve: Improve diagnostics for resolution ambiguities 2018-11-04 22:11:59 +00:00			note: `mac` could refer to the macro defined here
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-53269.rs:3:1`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			`\|`
			`LL \| macro_rules! mac { () => () }`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
resolve: Improve diagnostics for resolution ambiguities 2018-11-04 22:11:59 +00:00			note: `mac` could also refer to the unresolved item imported here
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-53269.rs:6:9`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| use nonexistent_module::mac;`
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
resolve: Tweak some articles in ambiguity diagnostics 2018-11-11 16:46:04 +00:00			= help: use `self::mac` to refer to this unresolved item unambiguously
resolve: Refactor away `MacroBinding` `fn resolve_legacy_scope` can now resolve only to `macro_rules!` items, `fn resolve_lexical_macro_path_segment` is for everything else - modularized macros, preludes 2018-08-17 23:38:51 +00:00
			`error: aborting due to 2 previous errors`

hide `--explain` hint if error has no extended info 2019-04-17 17:26:38 +00:00			`Some errors have detailed explanations: E0432, E0659.`
resolve: Unify reporting of ambiguity errors for macro paths 2018-08-20 21:34:30 +00:00			For more information about an error, try `rustc --explain E0432`.