Tony Arcieri
Tony Arcieri
Also if there are specific non-breaking changes you want, we can potentially backport them to the stable release series
I think I'd like to make an overall `stable` branch from where we initially switched to prerelease versions and keep changes there (also incorporating previous backports). It's something we probably...
Yes, though as noted earlier there are several prerequisites to release first: https://github.com/RustCrypto/traits/issues/1571
We are in the process of upgrading all of the crates in the @RustCrypto org to `rand_core` v0.9. You can track upstream progress here: https://github.com/RustCrypto/traits/issues/1642
Yes, this problem comes up every time there’s a breaking release to `rand_core` For now you can use v0.6
The latest release candidates use `rand_core` v0.9
Yes that sounds like a good idea cc @dhardy
As far as `FieldElement` access goes, `TwistedEdwardsPoint::Base` would be one way of exposing it, at least when the next release of the `group` crate is available: https://github.com/zkcrypto/group/pull/49/files#diff-df25442eb916a316f39ccb89f7d38163eb8ca60413100a61b2848b17a4aad175R21
`FieldElement` is otherwise deliberately not part of the public API, though could potentially be exposed as "hazmat", though personally I'd prefer to wait for `group`-based APIs to expose it
Given your need to couple to the internals either opening a PR or maintaining the fork sound like options. If you're in a hurry the latter sounds like the most...