-
Notifications
You must be signed in to change notification settings - Fork 116
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
Continues searching if a non-symbol matches a symbol link #901
Merged
d-ronnqvist
merged 4 commits into
apple:main
from
d-ronnqvist:non-symbol-match-to-symbol-link
May 3, 2024
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6abed54
Continues searching if a non-symbol matches a symbol link
d-ronnqvist 45a398b
Merge branch 'main' into non-symbol-match-to-symbol-link
d-ronnqvist b9badcf
Merge branch 'main' into non-symbol-match-to-symbol-link
d-ronnqvist cfa4103
Use an inner function to guarantee searchForNode return value validation
d-ronnqvist File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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 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 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.
Before, it was very easy to state that this method returned a
PathHierarchy/Error
. However, now that this method calls another very extensive method with its own inner method calls, it's more difficult to assure that this- Throws: Raises a PathHierarchy/Error if no match can be found.
is always true.I checked all the other throw statements inside
findNode
, and it seems like they all throw aPathHierarchy/Error
. However, since there are multiple nested calls, I find it very easy to mistakenly throw another type of error without noticing this comment.Any thoughts about this?
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 comment still holds true. All errors raised from
PathHierarchy/find(path:parent:onlyFindSymbols:)
arePathHierarchy/Error
. In the future when we eventually update to Swift 6 we can adopt typed throws here to have the compiler enforce this.