You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think all those execution details should be available to the client prior to execution. Do you think any client can be savings by assuming the code will not need those and only lazily populate evmc_tx_context on the first call to to get_tx_context?
The text was updated successfully, but these errors were encountered:
I believe it is good change. It saves us trouble caching this on VM side.
Also, this can be handled very efficiently on the Host side - it requires to create the tx_context once per block, and then update the 2 fields than depend on transaction. If you process transactions in parallel, you need multiple copies per execution thread.
I think all those execution details should be available to the client prior to execution. Do you think any client can be savings by assuming the code will not need those and only lazily populate
evmc_tx_context
on the first call to toget_tx_context
?The text was updated successfully, but these errors were encountered: