-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.6 release tracking ticket #681
Comments
With a prospective MSRV of 1.83 already, and the 2024 edition set to be stabilized in Rust 1.85 on 2025-02-20, I'm wondering if it makes sense to wait for that as well: https://doc.rust-lang.org/edition-guide/rust-2024/index.html Notably edition bumps are a time where the entire ecosystem makes a more concerted effort to bump MSRV. |
My two cents on this is: don't wait. Let the bigint project be its own thing and release when it's "internally" logical to do so. One option is to let the MSRV bump be a one-feature release (i.e. release 0.6 without |
Rust 1.83 is coming out on November 28th, a week away. We can at least wait for that. A release thereafter might make sense. |
Hey @tarcieri any update as to the release date? Also, is there a changelog?
I'm not sure if the original plan was to make such a hard-breaking release, and if you knew it would take so much effort to be upgraded, but in any case a thorough changelog that explains the breaking changes and their implications would ease my mind a lot. |
This is a list of release blockers for
crypto-bigint
v0.6.0, nearly all of which are final releases of dependencies which are currently in a prerelease state:const_mut_refs
stabilizationder
v0.8.0hybrid-array
v0.2.0rand_core
v0.9.0serdect
v0.3.0Int
feature tracking ticket #700core
core
naming conventions for bigint methods #693The text was updated successfully, but these errors were encountered: