Fix slab size when resetting mutable storable in OrderedMap #337
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates #292 #335
Changes
Recompute slab size by adding all element sizes instead of using the size diff of old and new element because
oldElem
can be the same storable when the same value is reset andoldElem.ByteSize()
can equalstorable.ByteSize()
.Given this, size diff of the old and new element can be 0 even when its actual size changed.
Also extracted map data slab prefix computation to a new function.
This is prep work for atree inlining to prevent a bug from surfacing.
main
branchFiles changed
in the Github PR explorer