Skip to content

In 2015 edition, mention the need for extern crate foo when failing to resolve use foo #97095

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
estebank opened this issue May 16, 2022 · 0 comments · Fixed by #97264
Closed
Assignees
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically D-edition Diagnostics: An error or lint that should account for edition differences. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@estebank
Copy link
Contributor

https://users.rust-lang.org/t/error-e0432-unresolved-import-serde/75707

@estebank estebank added A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. D-edition Diagnostics: An error or lint that should account for edition differences. labels May 16, 2022
@TaKO8Ki TaKO8Ki self-assigned this May 21, 2022
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Jun 1, 2022
…ailing-to-resolve-use-crate, r=estebank

Suggest `extern crate foo` when failing to resolve `use foo`

closes rust-lang#97095

r? `@estebank`
@bors bors closed this as completed in daedae7 Jun 1, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-resolve Area: Name/path resolution done by `rustc_resolve` specifically D-edition Diagnostics: An error or lint that should account for edition differences. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants