Skip to content
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

Parsing #56

Open
mverleg opened this issue May 13, 2018 · 2 comments
Open

Parsing #56

mverleg opened this issue May 13, 2018 · 2 comments
Assignees
Labels
compile priotity! High-priority issues that should be completed first

Comments

@mverleg
Copy link
Collaborator

mverleg commented May 13, 2018

This is the last Kotlin part. Part of #27

@mverleg mverleg added the priotity! High-priority issues that should be completed first label May 13, 2018
@mverleg mverleg self-assigned this May 13, 2018
mverleg added a commit that referenced this issue May 17, 2018
mverleg added a commit that referenced this issue May 18, 2018
mverleg added a commit that referenced this issue May 22, 2018
@mverleg mverleg mentioned this issue May 28, 2018
@mverleg
Copy link
Collaborator Author

mverleg commented Jun 10, 2019

Perhaps during the prototyping phase, quick iteration is more important than clear errors, performance or customization.

Therefore it might be good to use something like pest, with the possibility that it will be replaced by hand-written code when stabilization approaches.

@mverleg
Copy link
Collaborator Author

mverleg commented Jun 15, 2019

Another possibility is lalrpop, in which case this Python sample could be adapted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compile priotity! High-priority issues that should be completed first
Projects
None yet
Development

No branches or pull requests

1 participant