#20744: Polynomial encoder for GRS codes fails if variable name is not x
-------------------------------------+-------------------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.3
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dlucas/grs_polynomial_encoder_msg_space_fix|
9c3c1cde84fa9766f1335222d9a09695e5f99220
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jsrn):
I was wondering whether it would make more sense to have an option to give
the polynomial ring? But I'm not sure it would. For `ReedMullerCodes`
(which are in the making), one could argue that it *does* make sense
(since we otherwise need many names), and in this case, it would be
consistent that `ReedSolomonCode` follows the same pattern.
One could also, for usability, make a method `polynomial_ring()` on the
encoder which is an alias of `message_space()`.
--
Ticket URL: <http://trac.sagemath.org/ticket/20744#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
