-
Notifications
You must be signed in to change notification settings - Fork 24
feat: add TriePathIter for iterating over the nodes along a path #1367
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
base: main
Are you sure you want to change the base?
Conversation
6d39ab2 to
d710821
Compare
3e79cd6 to
99974a1
Compare
d710821 to
2446fa7
Compare
99974a1 to
dbb899d
Compare
2446fa7 to
787fe3c
Compare
rkuris
left a comment
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.
Let's chat about this and how it differs from the existing MerkleNodeIter. The existing code is tested heavily as it forms the basis of MerkleKeyValueIter.
If this code is better/faster/more generic, lets describe which and the motivation for a new iterator more clearly in the PR description.
dbb899d to
366441a
Compare
30e63e5 to
8b019d4
Compare
7cf3d26 to
9087e50
Compare
8b019d4 to
1136cc1
Compare
|
9087e50 to
63a3b3e
Compare
1136cc1 to
8a534ef
Compare
This is used to walk along a path to yield all of the edges. In proof verification, this is used to verify the paths of the proof are valid.