#18269: A new structure for experimentation on decoding: communication channels
-------------------------+-------------------------------------------------
Reporter: | Owner:
dlucas | Status: needs_review
Type: | Milestone: sage-6.7
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
coding theory | Work issues:
Keywords: | Commit:
Authors: | 2bc05906eb2db277bac427ec2ea55a47f95f1f26
Report Upstream: N/A | Stopgaps:
Branch: |
u/dlucas/channels |
Dependencies: |
-------------------------+-------------------------------------------------
Changes (by dlucas):
* status: needs_work => needs_review
Comment:
>If you look at the table of contents of coding you have
>[...]
>Not very nice. Though not for this ticket. Think about it for later on
the table of contents of code documentation is a mess! But of course the
priority is to clean the code.
I agree. It's definitely something to keep in mind.
>A more global remark: it is generally a bad strategy to implement an
isolated block of code and then to try to mix things later. Especially if
the code in itself is basically useless.
Got it!
I did the suggested changes in the code. I removed `__eq__`, as I do not
really picture a case in which one would need to compare two channels.
David
--
Ticket URL: <http://trac.sagemath.org/ticket/18269#comment:18>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
