-
Notifications
You must be signed in to change notification settings - Fork 2
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
Standalone parser with to json and back converters #4
Conversation
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.
this project seems to be down 😞
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.
@knopki wow, this is so C++ 😆
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.
@knopki why a standalone version is used, rather than an installable library?
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.
w.r.t.
Regenerate standalone lark parser after grammar.lark change: make parser
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.
@knopki why a standalone version is used, rather than an installable library?
Compiling a grammar is about 5 seconds. If you use lark
as a library, you'll either have to make the user suffer (compile to cache on the first run) or ship the cache with the package. When using the standalone version, almost the entire file is the result of compiling the grammar.
And the lack of runtime dependencies is more of a positive feature.
lark
parser