-
Notifications
You must be signed in to change notification settings - Fork 114
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
Step 11: kernel integration (put / delete split in contract details) #809
Conversation
- removed one of the set storage methods because it was not used
…nter exceptions on print
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
b9601bb
to
bfe1381
Compare
bfe1381
to
e29722f
Compare
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!
} | ||
|
||
// never used |
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.
delete?
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.
We may want to remove the full class, cause there are multiple classes used for repository test functionality. But this feels like a separate task.
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.
If this is the test class that ends up remaining after refactoring, the functionality may be reenabled.
/** | ||
* Sets the storage to contain the specified key-value mappings. | ||
* | ||
* @param storage The specified mappings. | ||
* @param storage the specified mappings | ||
* @apiNote Used for testing. |
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.
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.
I marked the fact that it was only used for testing so that maybe it gets removed from the interface during the refactoring. Then the tag can be added to the implementations.
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
Description
Last important integration step. Separating the put and delete in contract details to later allow the AVM to put bute arrays that are all 0 values.
Requires changes in aion_fastvm.
Type of change
Insert x into the following checkboxes to confirm (eg. [x]):
Testing
ContractDetailsCacheImpl
behaves correctly on put and deleteVerification
Insert x into the following checkboxes to confirm (eg. [x]):