Skip to content

Conversation

@tarcieri
Copy link
Member

It seems like the changes are backwards compatible with every crate except for elliptic-curve, where some reborrowing was required

It seems like the changes are backwards compatible with every crate
except for `elliptic-curve`, where some reborrowing was required
@tarcieri
Copy link
Member Author

FYI @baloo @dhardy

@tarcieri tarcieri merged commit 4be5aa4 into master Jan 19, 2026
79 checks passed
@tarcieri tarcieri deleted the rand_core/v0.10.0-rc-4 branch January 19, 2026 19:46
@baloo
Copy link
Member

baloo commented Jan 19, 2026

huum, no there is something fishy here, you shouldn't have to do that.

@baloo
Copy link
Member

baloo commented Jan 19, 2026

I think this is because CryptoRng no longer implies RngCore and that trait now has to be explicit.

I've opened #2197 to remove the extraneous references

tarcieri pushed a commit that referenced this pull request Jan 19, 2026
This fixes changes made in #2195

This is due to the refactor made in rand_core in
rust-random/rand_core#45 which dropped the
"trait dependency" between CryptoRng and RngCore
@dhardy
Copy link

dhardy commented Jan 20, 2026

I think this is because CryptoRng no longer implies RngCore and that trait now has to be explicit.

It very much should do. If it doesn't that's a bug. (I know the traits are written differently, but as best I can tell this is still implied.)

Self {
scalar,
mask: Scalar::<C>::random(rng),
mask: Scalar::<C>::random(&mut rng),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not keep Scalar::<C>::random(rng)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants