-
Notifications
You must be signed in to change notification settings - Fork 211
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
[kvdb-memorydb] Migrated code to 2018 edition, updated parking_lot #222
Conversation
It looks like @expenses signed our Contributor License Agreement. 👍 Many thanks, Parity Technologies CLA Bot |
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.
lgtm but I'm a bit worried about the parking_lot update.
kvdb-memorydb/Cargo.toml
Outdated
|
||
[dependencies] | ||
parking_lot = "0.6" | ||
parking_lot = "0.9" |
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.
We're on 0.8
in parity-ethereum
and I have a hunch that this could break things. If you feel like trying this change against the master branch over there, that'd be fantastic.
There are some breakages such as
Perhaps this should be version |
@expenses you mean change this crate to v0.2.0? If we upgrade parking_lot to a breaking version then yes. The best way imo would be to revert the parking_lot upgrade and get this merged, then we deal with upgrading the reps separately. And thanks again for your work here! :) |
Sure, I'll do that. |
See #143.