-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Rust: Account for attribute expansions in path resolution #20454
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
Merged
hvitved
merged 7 commits into
github:main
from
paldepind:rust/path-resolution-attribute-expansion
Sep 20, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c7a9cc5
Rust: Use annotations also for items in macro expansions
paldepind 32365fd
Rust: Account for attribute expansions in path resolution
paldepind 2c84b49
Rust: Update test expecations
paldepind a9d7662
Rust: Add path resolution test with attribute on impl block
paldepind 60ceb89
Rust: Add debug predicate for `ItemNode`
paldepind 72103ad
Rust: Fix spurious path resolution
paldepind afb6d30
Rust: Fix typo in superseded
paldepind File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,9 +25,9 @@ private module ResolveTest implements TestSig { | |
|
|
||
| private predicate item(ItemNode i, string value) { | ||
| exists(string filepath, int line, boolean inMacro | itemAt(i, filepath, line, inMacro) | | ||
| commmentAt(value, filepath, line) and inMacro = false | ||
| commmentAt(value, filepath, line) | ||
|
||
| or | ||
| not (commmentAt(_, filepath, line) and inMacro = false) and | ||
| not commmentAt(_, filepath, line) and | ||
| value = i.getName() | ||
| ) | ||
| } | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Actually, I think it is easier just to make
getRelevantLocatablepublic (I already do that in on of my PRs).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.
In this case I wanted to see the
ItemNodes in a given range.getRelevantLocatablewould give allLocateables wouldn't it?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.
Yes; perhaps your use case was different from mine; I would add calls to
Debug::getRelevantLocatablethroughout the source code when debugging.