Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Stabilisation of rand_core crate #386
Hi! I'm sorry for creating an issue when this isn't one, but I wasn't sure how else to get in contact. Feel free to close. (Also my work email is firstname.lastname@example.org and I'm in most of the Mozilla IRC rust channels as isis.)
In tor, we have C wrappers around OpenSSL's CSPRNG as well as some syscalls (when available). In order to avoid accidentally producing multiple CSPRNGs with the same state (we're using both C and Rust in the codebase right now, with some implementations duplicated/rewritten and others wrapped), we'd like to simply wrap our C code (tracking ticket). It seems like the best way to do this would be to implement traits from
Do you have any ideas when you might stabilise
Thanks! and keep up all the great work!
@dhardy Is does the releases, so I can only give my idea.
There is already a pre-release of
@dhardy: Would it make sense to release
Yes, I think releasing 0.1.0 soon should be fine.
Doc updates and optimisations can potentially land as a point release anyway so no issues there.
Lets open a PR to bump the version numbers (and changelog/readme), then if nothing comes up for a couple of days I'll make that the release — unless you want to do the