-
Notifications
You must be signed in to change notification settings - Fork 5
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
BoxedUint
support
#40
Conversation
ba18980
to
fc1467b
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #40 +/- ##
==========================================
+ Coverage 99.20% 99.23% +0.02%
==========================================
Files 9 9
Lines 1386 1433 +47
==========================================
+ Hits 1375 1422 +47
Misses 11 11 ☔ View full report in Codecov by Sentry. |
@tarcieri I think this concludes the initial support stage for |
fc1467b
to
899c81c
Compare
899c81c
to
f9f673d
Compare
f9f673d
to
b86c990
Compare
24444fb
to
2b44a1f
Compare
Published v0.6.0-pre.0. Before 0.6.0 proper I may tweak the public API a little with respect to how Also filed #41 to investigate the BoxedUint performance. |
This may supersede #39. It uses
*_like
constructors (see RustCrypto/crypto-bigint#533) instead of automatic widening, which I think is a safer approach.The 1024 bit safe prime generation is about 30% slower for
BoxedUint
compared toUint
. Not too bad for a start, but clearly there is room for improvement.@xuganyu96 sorry, tried to base it on your PR, but I guess I changed the first commit too much, and it's not assigned to you anymore.