-
Notifications
You must be signed in to change notification settings - Fork 163
use found disambiguation to calculate diagnostic range if present #1213
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
QuietMisdreavus
merged 5 commits into
swiftlang:main
from
QuietMisdreavus:collision-range-adjustment
May 9, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3de0e13
use found disambiguation to calculate diagnostic range if present
QuietMisdreavus 117350f
review: use all the non-overloadable symbol kinds
QuietMisdreavus ba5fff2
review: assert that solutions exist before iterating on them
QuietMisdreavus 1176cef
review: remove redundant assertion condition
QuietMisdreavus a7b2a37
review: add tests for wrong suffix and wrong name
QuietMisdreavus 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
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
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.
question: Is
.lookupCollisionthe only kind of value where this happened or should we add similar checks to the other types of errors as well?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.
It looks like the
rangeAdjustmentfeature is also used by theunknownDisambiguationandunknownNameerrors, which could also potentially be wrong. Would you like me to investigate these options in this PR, or land this as-is and investigate those 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.
Either way works. If it's easy to investigate and fix it might make sense to do it while all of this is fresh in the mind.
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.
I added tests for those cases to see if they would also have problems, and it looks like they're fine. 🤷♀️ I'll leave the tests in for posterity, but i didn't need to change anything for the cases i tested.