-
Notifications
You must be signed in to change notification settings - Fork 15
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
Extract incrementalmerkletree::testing
module to a separate incrementalmerkletree-testing
crate.
#113
Conversation
b23a5e6
to
d3db03f
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.
Partial review as of d3db03f (I'm still checking the large move).
If it turns out that the workspace change does require downstreams to raise MSRV, I would prefer that we explicitly raise MSRV in its own commit instead of implicitly doing.
I'd mildly perfer 1.64 instead of 1.70 for this PR (as that is the only necessary bump; it could be raised again in a subsequent PR as new features are needed).
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.
Reviewed d3db03f
This requires us to upgrade our MSRV to 1.64
…talmerkletree-testing` crate.
d3db03f
to
f6a5ae4
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 f6a5ae4
f6a5ae4
to
03a32d5
Compare
03a32d5
to
d663a8f
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.
Re-utACK d663a8f
This change will allow us to continue to move
incrementalmerkletree
andshardtree
development forward without having to continue to maintainbridgetree
compatibility withincrementalmerkletree::testing
after the nextincrementalmerkletree
release.