trie: make stacktrie not mutate input values #22673
Merged
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.
The stacktrie is a bit un-untuitive, API-wise: it mutates input values.
This is dangerous, and easy to get wrong if the calling code 'forgets' this quirk, so this PR fixes that behaviour. The first commit provides a testcase, and the second commit provides a fix. Naturally, the fix has an overhead.
With this PR:
Alternative fix:
With alternative fix:
With this PR in, though, we can make some other improvements to not always copy data on input. However, it should be noted that the stacktrie still needs the caller to not mutate the data from the outside, so we cannot remove e.g. example https://github.com/ethereum/go-ethereum/blob/master/core/types/hashing.go#L80:L83 (btw -- the ordinary trie behaves the same way, you're not allowed to mutate input values from the callsite)