Skip to content

Refactor Path Handling in Parser #8855

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
merged 4 commits into from
May 5, 2020
Merged

Conversation

odersky
Copy link
Contributor

@odersky odersky commented May 1, 2020

No description provided.

No need to start a separate scanner; we can simply use the existing prev/next logic.
@odersky odersky force-pushed the depscala-1 branch 3 times, most recently from c479686 to 3e39c73 Compare May 1, 2020 15:58
odersky added 2 commits May 1, 2020 18:00
Instead of passing a closure down, use one-token lookahead going froward.
This simplifies the logic of parsing paths.
Split off the parts of SimpleType that

 - can be applied to type arguments, or selected with #
 - can be used in a constructor

This gives a bit more precision for type and constructor parsing.
It's also a necessary step to be able to add types that are applied to
singletons.
@odersky odersky marked this pull request as ready for review May 1, 2020 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants