-
Notifications
You must be signed in to change notification settings - Fork 185
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
Vyper or something else #13
Comments
For some context, converging on the language syntax will probably mean that they have to write their own parser instead of depending on the python stdlib parser. IMHO, reliance on the stdlib parser was one of the things holding the language back and even encouraging patterns of corner-cutting that led to bad engineering practices. It would be great if the python vyper was willing to write a custom parser, but it might be a big ask. |
The official Vyper grammar is located here: https://github.com/vyperlang/vyper/blob/master/tests/grammar/vyper.lark Edit: I am working on an update to streamline the grammar a lot vyperlang/vyper#1827 |
The eventual idea is that if it's good enough to pass test suite, it should be good enough to start on a refactor of the compiler front end. I would eventually like to move to Lark fully: https://github.com/fubuloubu/vyper-redux/blob/master/vyper/ast.py#L229 details an idea of how this might look |
The python vyper compiler is continuing with development.
There are already choices in this codebase which make this version of vyper not syntactically compatible with the python one. For this reason I think we have two choices.
No urgency if we're good with option 2 (even if we don't end up going that way). More urgency if we want to put in the political work to converge the language syntax.
The text was updated successfully, but these errors were encountered: