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
VM/SM/Blockchain/Trie/EVM: Copy() -> shallowCopy() function renaming #2826
Conversation
Quick note: after an exchange with @jochem-brouwer we realized that the EVM copy() method also has state and therefore should be renamed as well. |
cb0bc1d
to
7c485a5
Compare
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
…to copy-function-renaming
Did a branch update here via UI |
Another branch update via UI |
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 looks pretty good, thanks a lot! 🤩
One thing: it would be good if we give this a mention in the direct code docs above the - now - shallowCopy()
methods - what the "shallow" part of the copy actually is, so that this gets a bit of a description, something like the following for EVM:
/**
* This method copies the EVM, current HF and EIP settings
* and returns a new EVM instance.
*
* Note: this is only a shallow copy and both EVM instances
* will point to the same underlying state DB.
*
* @returns EVMInterface
*/
Will merge though, this can be done in a small follow-up PR (also ok: alongside another PR).
Working on documentation update in #2855. |
TODO: