-
Notifications
You must be signed in to change notification settings - Fork 77
allow type params before navigation suffix #79
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
Open
brandonspark
wants to merge
1
commit into
fwcd:main
Choose a base branch
from
brandonspark:allow-type-params-before-navigation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
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.
Hm, I'm not quite sure how I feel about this workaround. While I understand that it's hard to parse, it seems to deviate quite a bit from the reference grammar and including the type arguments in the navigation suffix node (both of which are exposed), downstream consumers might have to rewrite the syntax tree quite a bit to get accurate results.
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 suppose it just comes down to how much you weigh being able to parse this versus the compromises we've already made with the syntax tree. For instance, this
call_suffix
workaround (which basically does the same thing, by embedding the optional type arguments in a different node of the tree) was worthy enough of being included, so I see this as adding just another case.I can keep thinking about it, but this seems like a rather pervasive parsing issue, from the things I've seen, and I'm not sure if we can make something truly faithful to the original syntax specification. At the end of the day, the Kotlin grammar is a reference for specification, but implementation may face some difficulties emulating it.