Open
Conversation
Member
|
Wouldn't it be better to introduce |
Member
Author
|
That would allow
|
e79fcb2 to
7890243
Compare
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.
CHANGELOG.mdentrySummary
Adds:
Motivation
We have removed
SeedableRng::from_os_rng()since the last release.SomeRng::try_from_rng(&mut getrandom::SysRng).unwrap()is not exactly convenient to use.We could put something like this under
getrandom, but it feels more appropriate withinrand(also allowing usage ofThreadRng).Details
This is also slightly contentious, but I feel it's useful enough to be worth having. We could add
trait SeedableRngExtinstead, but that would have significantly more API surface.