-
Notifications
You must be signed in to change notification settings - Fork 26
MerkleDbNode error definition + HexHash, move node_db_prefix
#470
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c4ef7ae
Make common MerkleHash options always inlined
malcolmgreaves 6ef5edf
+ HexHash, docs, borrow for prefix/suffix dir creation
malcolmgreaves 28c8541
refactor: new MerkleDbError type & wrapper
malcolmgreaves 71db754
bugfix
malcolmgreaves 3029b09
review feedback, move node_db_prefix, add test
malcolmgreaves 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
Some comments aren't visible on the classic Files Changed page.
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
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
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
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.
A couple things you could do for ergonomics if you wanted to:
MerkleHash:HexHashact like a&str, then you don't need a method that does an explicit conversion anymore:If you do both above, then this code becomes:
and then you could remove all of this:
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 like
to_hex_hashforMekleHash-- I'll add that one.For
&str, I want to be careful with this. In general, the intention is to not treat aHexHashas a string. I want there to be a little bit of friction so that a string can't be confused for a hexidecimal formattedMerkleHashvalue. With that context, I think having aDerefimplementation forHexHashwill make it too easy to break the type safety of theHexHashwrapper.I added the
as_strto make this prefix-suffix split function avoid twoStringallocations. 🤔 I could instead move this logic intoHexHash. That way I can avoid havingas_strall together and have the function return the 2-layered nested directories directly. I think this makes sense since this directory structure is a primary use case of hex-formatting the hash value.