-
Notifications
You must be signed in to change notification settings - Fork 40
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
Now prunes tries properly (and more aggressively!) without hack #97
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
6254d61
Finished logic for detecting trie collapses
BGluth bb29a5b
A few fixes related to branch collapse detection
BGluth 8bc8de4
Requested PR changes for #39
BGluth 6a8aee8
Extension nodes are now always not hashed if encountered
BGluth 7c4dd54
Mix of different cherry-picked fixes
BGluth d1b3f55
Impled additional logic to extract remaining child
BGluth cbf21ed
Cleanup from messy cherry picks
BGluth 8110160
Merge branch 'main' into aggressive_trie_pruning_finish
muursh a356d68
Apply suggestions from code review
BGluth 04d5e4b
Requsted PR changes for #97
BGluth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Just noticed it now, but why do we need
U512
? For the 65-Nibbles edge case? We probably would want to refactor it at some point, seems a bit wasteful to leverageU512
everywhere here (though out of scope for this PR).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.
Yeah exactly. It's for the 65
Nibble
edge case.I don't think I have a Github issue open for this (there was one in Jira), so I'll create one. Also worth having a discussion on the best way to implement this. If we care about performance, using a byte array might perform worse. I know
H256
uses a[u8; 32]
, butU256
s use[u64; 4]
. If I had to guess, sinceH256
don't support common operators (eg.+
,-
), they probably found that working withu64
s allowed them to implement a lot of operations with 64-bit instructions (vs. doing a bunch of operations to individual bytes). Probably worth talking to @dvdplm about this, as IIRC he worked onethereum-types
a good amount.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.
Created an issue for this (#104).