-
Notifications
You must be signed in to change notification settings - Fork 29
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
Upgrade dependencies #50
Conversation
Cargo.toml
Outdated
futures-core = { version = "0.3.0", default-features = false } | ||
lock_api = "0.3.2" | ||
parking_lot = { version = "0.10", optional = true } | ||
futures-core = { version = "0.3.5", default-features = false } |
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.
Given this doesn't really use a lot from futures maybe it should stay with the old version or just use ^0.3
. Reduces the chances for dependendy conflicts.
Cargo.toml
Outdated
futures = { version = "0.3.5", default-features = true, features = ["async-await"] } | ||
futures-test = { version = "0.3.5", default-features = true } | ||
pin-utils = "0.1.0" | ||
criterion = "0.3.3" |
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.
This, crossbeam, and rand should be pushed to the newest version with the same minor number anyway. Don't see a lot of benefit in tracking fix versions.
No concern regarding more explicit updates of async-std and tokio however, since there seem to have been quite a bit of changes.
I just ran cargo upgrade without thinking. The only upgrades I care about is:
|
c9f328a
to
21f2829
Compare
Co-authored-by: Matthias Einwag <matthias.einwag@live.com>
How about a release for this, and other recent merges? |
No description provided.