-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix false positive for typoed crate or module suggestion #90125
Fix false positive for typoed crate or module suggestion #90125
Conversation
I could fix this problem for modules but not for crates. I used |
This comment has been minimized.
This comment has been minimized.
ca60a5a
to
dd8bb96
Compare
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #90598) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look reasonable! Apologies for the delay in reviewing. There was a CI failure when I last looked at this PR that needed addressing, and a recent change introduced some merge conflicts. Could you try and rebase on top of master and make sure the tests all succeed?
fix false positive typoed crate or module suggestion
dd8bb96
to
b5caa1e
Compare
This comment has been minimized.
This comment has been minimized.
@estebank This PR solves a problem for modules but not for extern crates. I tried using For example: |
help: there is a crate or module with a similar name | ||
| | ||
LL | use my_core::mem; | ||
| ~~~~~~~ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, these lines should not be included in stderr because my_core
is defined in a decl_macro a
.
☔ The latest upstream changes (presumably #94121) made this pull request unmergeable. Please resolve the merge conflicts. |
@TaKO8Ki any updates on this? |
Closing this due to inactivity |
@TaKO8Ki feel free to reopen or refile when you have time again! |
follow up of #89347
closes #89592
closes #76208
r? @estebank