#19422: A new structure for Punctured Codes
-------------------------------------+-------------------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.2
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: David Lucas | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dlucas/punctured_codes | cef203fb5010d120386968f432648a60338c9fcc
Dependencies: #19653 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by dlucas):
Hello,
The user can now pass either an Integer, an int, a list or a set to
`PuncturedCode`. The internal representation is a set. I added a few extra
sanitization tests, so if one passes a list/set of anything but
ints/Integers, an exception is raised.
I also reinstated the list representation of the punctured positions for
str methods.
Remark:
for now, `punctured_positions` (the getter for `positions`) always return
a set, even if one passed an int/Integer/list at construction time. I
think it's fine like that, but if you think it can be confusing/annoying
for the user, I can change its behaviour so it returns the exact data one
passed at construction time.
This is still open for review.
Best,
David
--
Ticket URL: <http://trac.sagemath.org/ticket/19422#comment:26>
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.
