-
Notifications
You must be signed in to change notification settings - Fork 2k
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
CHIA-902 make Program.run() and Program.run_with_cost() default to enabling all the most recent features #18370
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.
See comments
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
1 similar comment
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
There doesn't seem much difference now between |
Yeah, as I mentioned above maybe we consider deprecating it. |
Waiting on merge for all conversations to reach a resolution. |
the difference is that |
Purpose:
This is a follow-up on #18287
This came out of a conversation with @trepca . Testing puzzles that use features from recent soft-forks (and the hard fork) is made more difficult because the default
run()
functions don't enable those features. This patch fixes that by enabling everything.It also runs in mempool-mode by default.
Additionally, a new
run()
variant is added to control exactly which features (flags
) are enabled.Current Behavior:
Program.run()
does not support new opcodes, and ignores unknown ones.New Behavior:
Program.run()
does supports new opcodes, and fails on unknown ones.