Skip to content

Updates for crypto-bigint v0.7.0-rc.27#114

Merged
fjarri merged 1 commit intoentropyxyz:masterfrom
tarcieri:bump-crypto-bigint
Feb 12, 2026
Merged

Updates for crypto-bigint v0.7.0-rc.27#114
fjarri merged 1 commit intoentropyxyz:masterfrom
tarcieri:bump-crypto-bigint

Conversation

@tarcieri
Copy link
Contributor

@tarcieri tarcieri commented Feb 11, 2026

Release PR: RustCrypto/crypto-bigint#1204

Includes updates for the following breaking changes:

  • Renamed nlimbs! => nlimbs (i.e. macro replaced with const fn)
  • Renamed UnsignedMontyForm => UnsignedWithMontyForm
  • Concat/ConcatMixed merged; Split/SplitMixed replaced with Split/SplitEven
  • Use crypto_bigint::cpubits macro (re-export from cpubits crate) for 32-vs-64-bit selection

Also includes a bump to rand/rand_core v0.10

@tarcieri tarcieri changed the title [WIP] Bump crypto bigint [WIP] Bump crypto-bigint Feb 11, 2026
@tarcieri tarcieri force-pushed the bump-crypto-bigint branch 2 times, most recently from be04ff4 to a518cb3 Compare February 11, 2026 20:25
@codecov
Copy link

codecov bot commented Feb 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.71%. Comparing base (d51e90f) to head (ac38024).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #114   +/-   ##
=======================================
  Coverage   98.71%   98.71%           
=======================================
  Files          14       14           
  Lines        1874     1874           
=======================================
  Hits         1850     1850           
  Misses         24       24           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tarcieri
Copy link
Contributor Author

tarcieri commented Feb 11, 2026

Perhaps we can get RustCrypto/crypto-bigint#1191 in with this too /cc @andrewwhitehead

@tarcieri tarcieri force-pushed the bump-crypto-bigint branch 3 times, most recently from 992bcb1 to 85a7b9a Compare February 12, 2026 15:59
@tarcieri tarcieri changed the title [WIP] Bump crypto-bigint Updates for crypto-bigint v0.7.0-rc.27 Feb 12, 2026
@tarcieri tarcieri marked this pull request as ready for review February 12, 2026 15:59
Release PR: RustCrypto/crypto-bigint#1204

Includes updates for the following breaking changes:
- Renamed `nlimbs!` => `nlimbs` (i.e. macro replaced with `const fn`)
- Renamed `UnsignedMontyForm` => `UnsignedWithMontyForm`
- `Concat`/`ConcatMixed` merged; `Split`/`SplitMixed` replaced with
  `Split`/`SplitEven`
- Use `crypto_bigint::cpubits!` macro (re-export from cpubits crate) for
  32-vs-64-bit selection

Also includes a bump to `rand`/`rand_core` v0.10
@tarcieri
Copy link
Contributor Author

Alright, that should be everything, and I went ahead and squashed.

Comment on lines +65 to +67
[lints.rust.unexpected_cfgs]
level = "warn"
check-cfg = ['cfg(cpubits, values("16", "32", "64"))']
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This little bit is unfortunately a viral property of the cpubits crate. It allows the selection to be overridden using e.g. --cfg cpubits="64", and in order for that to work any crate which uses the cpubits! macro needs this configured (and it needs to include 16 since the macro emits it as an option, even though selecting 16-bits for crypto-bigint will cause a compile error)

@fjarri fjarri merged commit 7b4d1da into entropyxyz:master Feb 12, 2026
12 checks passed
@tarcieri tarcieri deleted the bump-crypto-bigint branch February 12, 2026 22:11
@tarcieri
Copy link
Contributor Author

@fjarri awesome, thank you!

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.

3 participants