-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
resolve: Improve candidate search for unresolved macro suggestions #62684
Conversation
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.
LGTM, r=me if you're happy with this.
@bors r=davidtwco |
📌 Commit 4ffa0bb50dd9c48360c9b3d40985f830800ce724 has been approved by |
☔ The latest upstream changes (presumably #62669) made this pull request unmergeable. Please resolve the merge conflicts. |
Also move it into the crate root, it's no longer used for macros only
… is enabled Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros.
@bors r=davidtwco |
📌 Commit 1b4fbfc has been approved by |
resolve: Improve candidate search for unresolved macro suggestions Use same scope visiting machinery for both collecting suggestion candidates and actually resolving the names. The PR is better read in per-commit fashion with whitespace changes ignored (the first commit in particular moves some code around). This should be the last pre-requisite for #62086. r? @davidtwco
☀️ Test successful - checks-azure |
Use same scope visiting machinery for both collecting suggestion candidates and actually resolving the names.
The PR is better read in per-commit fashion with whitespace changes ignored (the first commit in particular moves some code around).
This should be the last pre-requisite for #62086.
r? @davidtwco