-
-
Notifications
You must be signed in to change notification settings - Fork 788
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
Add opcodes and opcodes_runtime flags to compiler #1255
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.
It would be nice to have a short test to show off how this works. (I'd love for it to be a doctest, and actually use them)
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, just fix the linting errors ;)
@fubuloubu doc tests are great for a quick test suite, but in general I think it just adds too much clutter on a code base - especially since we have a very extensive test suite already. |
Doctests are nice because they keep the docs up to date |
oops! |
What's the difference between |
If you are familiar with
|
What I did
opcodes
andopcodes_runtime
flags to the compilerHow I did it
PUSH
,SWAP
andDUP
opcodes tovyper/opcodes.py
get_opcodes
tovyper/compiler.py
opcodes
andopcodes_runtime
tooutput_formats_map
invyper/compiler.py
bin/vyper
How to verify it
vyper -f opcodes examples/crowdfund.vy
vyper -f opcodes_runtime examples/crowdfund.vy
Description for the changelog
opcodes
andopcodes_runtime
flags to the compilerCute Animal Picture