-
Notifications
You must be signed in to change notification settings - Fork 146
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.
Lets go
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.
Looks very good to me.. didn't test it, but it's very similar to what I expected.
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.
Testing looks good, but address looks very big on practice... a helpful alternative would be PUSHA and PUSHA_L
No. I won't provide _L for every opcodes. I will only do that for the most used opcodes. |
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.
Did you consider use it with Interop<Pointer>
instead of create a new stack item?
I think it is not related to interop. So it doesn't make sense to use intero. |
I agree that Interop is for external things Shargon... some internal neo-vm system may not even use Interops, so it's necessary to keep it self-contained. |
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.
Looks good, and tested.
Closes #190