Remove Clone for StdRng, new bound for ReseedingRng #1677
Merged
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.mdentrySince
Clonesupport was removed forchacha20(RustCrypto/stream-ciphers#462) we must removeCloneforStdRng.For
ReseedingRng, we could:Clonesupport withChaCha*Core.Rsdr: RngCore(i.e. that the reseeder is infallible) to allow seeding a newinnerRNG on clone.Clonesupport entirely.I opted for (4) since I suspect this feature has very little usage anyway. If users request that
Clonesupport be restored we can re-evaluate based on the reported use-case and implement it in a patch release.