Repository navigation
deps: move to rand 0.10 - #18
Merged
Merged
Conversation
The 0.9 and 0.10 renames removed `rand::RngCore` and `thread_rng`, so the upload filler now calls `rand::fill` and the multipart boundary calls `RngExt::random_range`. Both still draw from the thread RNG, so the payload is the same uniform bytes as before.
This file contains hidden or 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
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.
Supersedes #17, which bumped the crate without the API changes 0.9 and 0.10 need and failed to build everywhere.
rand::RngCoreandthread_rngare gone, so the upload filler callsrand::filland the multipart boundary callsRngExt::random_range. Both still draw from the thread RNG: gzip on an 8 MiB payload gives byte-identical compressed sizes before and after, and both expand it, as uniform bytes should.