-
-
Notifications
You must be signed in to change notification settings - Fork 808
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
feat[venom]: add venom parser #4381
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
🚀 |
@charles-cooper btw how I would I toggle optimizations on-off for faster venom compilation? |
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.
very slick -- much simpler than i was expecting! left a few comments
i think it would be good to have a couple test cases! e.g. in |
@charles-cooper should be ready to merge now |
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.
lgtm. a couple things for future scope:
- make data section optional in the grammar
- make entry block optional in the grammar (similarly to llvm)
- more output formats (
-f asm, opcodes, bytecode
)
What I did
I added a "frontend" for venom, allowing you to compile independent venom files.
How I did it
I defined a new grammar (a bit simpler than what the readme initially suggested) & parser using the
lark
parser generator library.How to verify it
Run the
venom
CLI against the example in the readme by putting it in aexample.venom
file and runningvenom example.venom
Commit message
Description for the changelog
Added independent CLI for compiling venom
Cute Animal Picture