Adjust Logic In Merkle DB History #1310
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
No reason to do a search through the history entries if we know the start root entry is before the end root entry. This will be the case most of time since having the same root in the history multiple times should be pretty rare in normal usage.
dboehm-avalabs
changed the title
danlaine
reviewed
Apr 10, 2023
danlaine
approved these changes
Apr 10, 2023
darioush
approved these changes
Apr 10, 2023
Co-authored-by: Darioush Jalali <darioush.jalali@avalabs.org>
abi87
pushed a commit
that referenced
this pull request
Apr 13, 2023
Co-authored-by: Darioush Jalali <darioush.jalali@avalabs.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No reason to do a search through the history entries if we know the start root entry is before the end root entry. This will be the case most of time since having the same root in the history multiple times should be pretty rare in normal usage.