- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 559
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
Inconsistency in polynomial .reverse(n) #15077
Comments
Stopgaps: inconsistentAnswer |
comment:6
This is obsolete. |
comment:7
There remain two issues: unifying the documentation, and also the version for |
Changed stopgaps from inconsistentAnswer to none |
comment:8
There remained actually more issues. The issue for
I hope I didn't forgot anything! |
Author: Bruno Grenet |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:10
ok, let it be |
Reviewer: Frédéric Chapoton |
Changed branch from u/bruno/15077_reverse_consistency to |
The optional argument of the
.reverse()
method of univariate polynomials is interpreted inconsistently through different classes.Rationals interpret is as "length":
The docstring for generic polynomials (inherited by
CC
, number fields,Polynomial_GF2X
,Polynomial_ZZ_pEX
, ...) says:but the behaviour is inconsistent with it
Polynomial_zmod_flint
andPolynomial_integer_dense_flint
have the exact same docstring and behaviour, though they do not inherit.reverse()
from the generic class:Reals take no optional argument. The docstring says
and the behaviour is consistent with it
In my opinion the best behaviour is the one of the generic class, but the docstring should be amended to something similar to the last one, which is the proper mathematical definition. The behaviour of rationals should be corrected to conform to the other classes.
CC: @mezzarobba @jhpalmieri
Component: commutative algebra
Keywords: polynomial univariate reverse
Author: Bruno Grenet
Branch/Commit:
bd32a84
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/15077
The text was updated successfully, but these errors were encountered: