-
Notifications
You must be signed in to change notification settings - Fork 82
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: execute #430
feat: execute #430
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.
Can we test this new function?
Should we? I think it should be part of a bigger testing strategy. Or should I just send an empty bytecode? |
I see, may make more sense to test interpreter.run then |
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
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Resolves: #424
What is the new behavior?
starknet_address
field from the contextexecute
functionexecution::execute
function that the core contract will call #424Does this introduce a breaking change?