-
Notifications
You must be signed in to change notification settings - Fork 148
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
Failing assertion while multiplying two BigUints #187
Comments
This is definitely a bug in the implementation, not something you did or should have done. The comments around that assertion are just development details from #133. In fact, @koverstreet if you see this, I'd appreciate if you can take a look. FWIW, |
I'll dig into it first thing tomorrow. On Tue, Apr 19, 2016 at 7:37 PM, Josh Stone notifications@github.com
|
When x.len() and y.len() are both equal and odd, we have x1.len() + y1.len() + 1 (the required size to multiply x1 and y1) > y.len() + 1 This fixes rust-num#187
When x.len() and y.len() are both equal and odd, we have x1.len() + y1.len() + 1 (the required size to multiply x1 and y1) > y.len() + 1 This fixes rust-num#187
bigint: Fix calculation of size for multiply temporaries When x.len() and y.len() are both equal and odd, we have x1.len() + y1.len() + 1 (the required size to multiply x1 and y1) > y.len() + 1 This fixes #187
Do not panic in to_value
The code above crashes at this assertion in num-bigint:
while it runs fine with one digit less in
s
. The same problem occurs with an unchecked multiplication.I am not sure how to interpret the comment below the assertion; is there an allocation I should make manually?
The text was updated successfully, but these errors were encountered: