Upgrade rand 0.5.2 -> 0.6.4 #53
Merged
Conversation
This file contains 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
|
Thanks. |
psmit
pushed a commit
to psmit/tungstenite-rs
that referenced
this pull request
Nov 14, 2019
Introduce `Message::Close` support and return `Async::Ready(None)` when the stream is ended
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tokio & futures 0.1 ecosystem seems to have moved to rand 0.6 except for Tungstenite. At least in my toyproject, Tungstenite is the only dependency that still depends on rand 0.5.2. This patch resolves the only remaining duplicate transitive dependency in my project (since no two rand versions are required after applying this patch).