Skip to content
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

Open
2 of 9 tasks
Tracked by #681
erik-3milabs opened this issue Oct 29, 2024 · 11 comments
Open
2 of 9 tasks
Tracked by #681

Int feature tracking ticket #700

erik-3milabs opened this issue Oct 29, 2024 · 11 comments

Comments

@erik-3milabs
Copy link

erik-3milabs commented Oct 29, 2024

Related

Features

@ycscaly
Copy link
Contributor

ycscaly commented Nov 1, 2024

@tarcieri with #695 merged to signed-int, whats the plan for this feature? Specifically, will it be included in the next release? Could be helpful esp. because of comparability other crates like elliptic-curves depending on crypto-bigint

@tarcieri
Copy link
Member

tarcieri commented Nov 1, 2024

@ycscaly yeah, we should be able to get at least a preliminary implementation into the release and then we can additively improve it.

I went ahead and added it to the list in #681

@ycscaly
Copy link
Contributor

ycscaly commented Nov 1, 2024

@ycscaly yeah, we should be able to get at least a preliminary implementation into the release and then we can additively improve it.

I went ahead and added it to the list in #681

Great thanks!

@tarcieri
Copy link
Member

tarcieri commented Jan 6, 2025

I'm planning on trying to wrap up crypto-bigint v0.6.0 stable, and I'd like to save this for crypto-bigint v0.7, FYI.

Fortunately, all work is happening on the signed-int branch.

@ycscaly
Copy link
Contributor

ycscaly commented Jan 6, 2025

I'm planning on trying to wrap up crypto-bigint v0.6.0 stable, and I'd like to save this for crypto-bigint v0.7, FYI.

Fortunately, all work is happening on the signed-int branch.

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.
We are planning to lunch our product very soon, and would be better to have this as part of a release if possible.

Thanks!

@tarcieri
Copy link
Member

tarcieri commented Jan 6, 2025

Aah, well then. We can potentially merge the signed-int branch, although there are still a few outstanding PRs and work seems to have stalled.

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.

@fjarri
Copy link
Contributor

fjarri commented Jan 6, 2025

What breaking changes do signed integers introduce?

@tarcieri
Copy link
Member

tarcieri commented Jan 6, 2025

As far as I'm aware, they're completely additive

@fjarri
Copy link
Contributor

fjarri commented Jan 6, 2025

So they can probably be added in 0.6.1 which would be much easier to handle in the dependencies?

@tarcieri
Copy link
Member

tarcieri commented Jan 6, 2025

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.

@ycscaly
Copy link
Contributor

ycscaly commented Jan 6, 2025

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?

erik-3milabs added a commit to erik-3milabs/crypto-bigint that referenced this issue Jan 7, 2025
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

No branches or pull requests

4 participants