-
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
New clvm generator api #9645
New clvm generator api #9645
Conversation
b4dff31
to
d053ae5
Compare
This pull request fixes 2 alerts when merging d053ae5 into 659f4f4 - view on LGTM.com fixed alerts:
|
0a87589
to
dc2ad48
Compare
if r.seconds_relative > 0: | ||
add_int_cond(conditions, ConditionOpcode.ASSERT_SECONDS_RELATIVE, r.seconds_relative) | ||
for cc in r.create_coin: | ||
if cc[2] == b"": |
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 is a slight difference. the new clvm_rs API always returns a 3-tuple with the last element being bytes
. If there is no hint, the bytes
is empty. However, previously, an empty atom was a valid hint, distinct from no hint at all.
Since hints aren't consensus critical, I don't think this really matters, but it meant I had to change the test_rom.py
below.
dc2ad48
to
f0efdd3
Compare
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.
Okay, I think I get it.
It uses the more compact return value from
run_generator2()
and converts it to our internal (more verbose) conditions format.