We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In EVM the caller must define the available space for return values.
In the current EVM2 design this is carried over, however it could be improved:
call
return
callstore
callResultCopy
callResultSize
It is a rough design, but it could be ironed out.
The text was updated successfully, but these errors were encountered:
I think this is related.
Sorry, something went wrong.
Solved by ethereum/EIPs#211
No branches or pull requests
In EVM the caller must define the available space for return values.
In the current EVM2 design this is carried over, however it could be improved:
call
doesn't defines the return value spacereturn
doesn't writes the value to the caller's memory space (I understand this today can depend on the VM anyway)return
places the values into an intermediate, in-memory storage (callstore
) and the contract is charged according to the size of thiscallResultCopy
is introduced for copying betweencallstore
and the caller's memory space (andcallResultSize
to retrieve the total size)callstore
is erased when acall
is executedIt is a rough design, but it could be ironed out.
The text was updated successfully, but these errors were encountered: