-
Notifications
You must be signed in to change notification settings - Fork 16
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
Release shardtree version 0.6 #127
Conversation
Allow `no_std` use of `incrementalmerkletree`
03ec3d3
to
3b21d21
Compare
3b21d21
to
04280c4
Compare
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.
utACK
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.
utACK 04280c4 with nit
@@ -18,7 +18,7 @@ categories = ["algorithms", "data-structures"] | |||
|
|||
[workspace.dependencies] | |||
# Intra-workspace dependencies | |||
incrementalmerkletree = { version = "0.8", path = "incrementalmerkletree" } | |||
incrementalmerkletree = { version = "0.8.1", path = "incrementalmerkletree" } |
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.
As noted in my other comment, I don't think this is actually necessary; cargo
will consider 0.8.0
and 0.8.1
as compatible, and if you're not in a no-std
environment then 0.8.1
contains nothing that you need (so this is just an overconstraint).
If, by contrast, the being-published shardtree
depended on a new API exposed by incrementalmerkletree
then this would be the correct way to express the dependency.
No description provided.