-
-
Notifications
You must be signed in to change notification settings - Fork 552
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
faster is_prime #16878
Comments
New commits:
|
Branch: u/vdelecroix/16878 |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:3
I would prefer not to include stuff from |
Reviewer: Jeroen Demeyer |
comment:4
Can you also change the value of |
comment:5
Instead of changing
accomplish the same thing? |
comment:6
Thanks for the remark. One question: are we sure that 264 fits into an unsigned long on any platform? Otherwise we can not safely call
Vincent |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Dependencies: #15767 |
comment:9
I don't think we should lower Personally, I would assume that |
comment:10
Also, you wrote "set set" instead of "set". |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
This is bikeshedding I know, but wouldn't
be easier to understand? |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:60
Now all doctests pass. |
comment:61
|
comment:62
Replying to @videlec:
Yes, this was discussed on
I assume that |
comment:63
Replying to @jdemeyer:
True, I forgot about here and it is this thread.
I see... I do not like the fact that we avoid pari
What do you think? |
comment:64
To be honest, I think introducing |
This comment has been minimized.
This comment has been minimized.
comment:67
The buildbot is complaining about a digit
Might be related to the doctest failure in pari update in #16997. |
comment:69
Merges cleanly with #16997 and all tests pass! Cool. Vincent |
Changed branch from u/jdemeyer/16878 to |
Changed commit from |
Right now to test if a Sage integer is prime it is faster to call
prime_range
rather than.is_prime()
...versus
The patch does some tiny modifications in
integer.pyx
and we getWe also modify
is_prime_power()
to returnFalse
for 1 and raise an error for non-integral rationals like1/2
.See also this sage-devel discussion.
Depends on #16997
CC: @nathanncohen
Component: number theory
Author: Vincent Delecroix, Jeroen Demeyer
Branch:
1f8abd9
Reviewer: Jeroen Demeyer, Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/16878
The text was updated successfully, but these errors were encountered: