Add AllowedRng trait #187
Merged
Add AllowedRng trait #187
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
benr-ml
requested review from
huitseeker,
kchalkias,
joyqvq and
jonas-lj
as code owners
jonas-lj
approved these changes
Oct 31, 2022
kchalkias
approved these changes
Oct 31, 2022
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.
We should be more restrictive with the RNG we work with. This adds a trait for that.
(Updating the existing APIs will be done in a follow up PR).
The default for StdRng and ThreadRng is ChaCha12 (rust-random/rand#932)
Ideally our callers should use something like StdRng::from_rng(rand::rngs::OsRng) or just thread_rng, but for now we don't restrict that.