-
Notifications
You must be signed in to change notification settings - Fork 57
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
Int
feature tracking ticket
#700
Comments
I'm planning on trying to wrap up Fortunately, all work is happening on the |
Why can't we have the signed integers on 0.6? There's quite a bit already implemented here, and we are actively using it. Thanks! |
Aah, well then. We can potentially merge the If it doesn't make it in, we'll be able to merge it in a v0.7 release, which I would expect some time in Q2 2025. |
What breaking changes do signed integers introduce? |
As far as I'm aware, they're completely additive |
So they can probably be added in 0.6.1 which would be much easier to handle in the dependencies? |
Sure, no need to block a v0.6 release. It would probably be good to get a PR to merge the branch open first so we can confirm there aren't any breaking changes, though. |
Sounds like a good in-between solution. @erik-3milabs can you open this PR? |
Related
Int
- sign-and-magnitude #694 (abandoned attempt involving sign-magnitude representation),Features
add
,sub
,mul
,div
Int
- two's complement #695and
,or
,xor
,not
,shl
,shr
Int
- Bit ops #697Int::square
operationsInt
- square operations #724vartime
divisionInt
- vartime division operations #725mul_uint
,div_uint
Int
-Int
-Uint
interoperability. #726from_be_slice
,from_le_slice
)gcd
Int
- gcd #698xgcd
Int
- two's complement #695 (comment))The text was updated successfully, but these errors were encountered: