-
Notifications
You must be signed in to change notification settings - Fork 13.4k
bigint add function cause Segmentation fault #10288
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
Comments
@cmr has run this testcase on some months-old compilers, and it still crashes with them; so it looks like this has existed forever and isn't a (recent) regression. (Just as a general data point.) |
This causes a failure for me:
|
Aha, I must have fixed this with the check-for-overflow. I'll add tests for this. |
I don't think this is fixed, the fundamental problem of the bigint implementation of to_str being wrong is still there. |
…ro_wrapper, r=llogiq Add the `transmute_int_to_non_zero` lint Fixes rust-lang#10288 This adds a new complexity lint `transmute_int_to_non_zero` which checks for transmutes to any of the `NonZero*` types, and suggests their `new_unchecked` method instead. r? `@llogiq` changelog: New lint: [`transmute_int_to_non_zero`]
i worked with rust(bf98981)
i try to use bigint module. but bigint.add function cause segfault in some cases.
the cases is below
The text was updated successfully, but these errors were encountered: