-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Fix finite field modulus handling #16983
Comments
This comment has been minimized.
This comment has been minimized.
Dependencies: #16934 |
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
Branch: u/jdemeyer/ticket/16983 |
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:9
I get a failing doctest in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
New commits:
|
comment:15
There is something missing here:
|
comment:16
Otherwise, this looks fine to me and all tests pass. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
Replying to @jpflori:
I just moved that sentence, in fact it dates back to
New commits:
|
Reviewer: Jean-Pierre Flori |
comment:19
Ok, looks good to me. |
Changed branch from u/jdemeyer/ticket/16983 to |
For prime finite fields, we should support a custom modulus (internally in Sage, we don't need to use this modulus in the backend):
We should also make the modulus monic:
(the Givaro backend does this implicitly)
The patch does the above, with lots of cleaning up.
Depends on #16934
CC: @pjbruin @jpflori
Component: finite rings
Author: Jeroen Demeyer
Branch/Commit:
0d9b5cc
Reviewer: Jean-Pierre Flori
Issue created by migration from https://trac.sagemath.org/ticket/16983
The text was updated successfully, but these errors were encountered: