Fix symbol link parsing bug for -(_:_:)
operators with hash disambiguation
#739
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.
Bug/issue #, if applicable: rdar://113870038
Summary
Fix a bug where path component names wasn't consistently parsed depending on if the path component had a hash disambiguation or not. This resulted in subtraction operators (
-(_:_:)
) parsing as an empty name when the link had a hash disambiguation.Dependencies
None
Testing
Define a public type with
-(_:_:)
operators, for example:Link to
MyNumber/-(_:_:)-abc123
. After correcting the hash (which depends on the module name where this symbol is defined) link should resolve successfully.Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
./bin/test
script and it succeeded[ ] Updated documentation if necessary