-
Notifications
You must be signed in to change notification settings - Fork 143
Use hash writer for aristo computeKey #3572
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
Open
chirag-parmar
wants to merge
14
commits into
master
Choose a base branch
from
hash-writer-aristo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
7b4e814
incomplete
chirag-parmar b383533
commented code
chirag-parmar 2253512
use similar structure to ordered trie
chirag-parmar 60f5dad
comment
chirag-parmar c92907b
reintroduce the line
chirag-parmar 1e9f6ed
Remove hack.
bhartnett 13bc9b7
Merge branch 'master' into hash-writer-aristo
bhartnett 3dc24fa
Remove unneeded usages of untyped. Update encodeExt to a func to prev…
bhartnett 157f1a4
review
chirag-parmar 126c0a8
Remove usages of auto in encodeLeaf.
bhartnett 184a373
fix imports
chirag-parmar 2246c31
Make encodeLeaf a func and store hashKeys in encodeBranch.
bhartnett 0419fde
Update execution_chain/db/aristo/aristo_compute.nim
bhartnett 9f71e5e
Merge branch 'master' into hash-writer-aristo
bhartnett 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 hidden or 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.
doesn't this call to
wrapEnconding
depend onleafData
being of a particular type? if yes, why useauto
?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'm not sure about
wrapEncoding
but the reason I changed this line was that we are passing a type account or slot and don't need to pass in a block of statements. Perhaps it would be better to make it even more strict and useAccount | UInt256
as the type.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.
ok - it feels odd that it should be needed cc @chirag-parmar - ie
append
should be able to figure this out ideally - but it seems to work, so ..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.
Apologies for the late reply. the call to
wrapEncoding
doesn't depend on theleafData
being of a particular type. Only leaf nodes have nested serializations i.e. Serializing an object/list/tuple that already has a serialized rlp value in it.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 didn't understand what it must be able to figure out.
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 think what I would have expected maybe is a call like
appendEncoded(leafData)
which does the extra round of encoding of the passed-in item -wrapEncoding
looks like an internal low-level operation, specially with that number being passed in, because presumably it must be followed up with actual data - that gives the caller an unnecessary opportunity to use it the wrong wayThere 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.
makes sense actually. status-im/nim-eth#813