#16553: Clean IncidenceStructure
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: combinatorial | Resolution:
designs | Merged in:
Keywords: | Reviewers:
Authors: Nathann Cohen, | Work issues:
Vincent Delecroix | Commit:
Report Upstream: N/A | b51512d642a603ea91d9358ea3d7877f184938d0
Branch: public/16553 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:65 ncohen]:
> > Thanks. What should we do for `is_t_design`?
>
> Well the interface is nice, so why don't we just move the code of
`_t_design_parameters` into it ?
Hmmmm. There are plenty of `if condition: return blah` in
`_t_design_parameters`. Duplicating the code in `is_t_design` as many
times would be awful.
> Also, what about all the tuple stuff ? I think I asked this question 3
times already.
Yes, yes, yes. Either we hold immutable stuff or we copy on output. Note
that I introduced the keyword copy which allows you to feed it with list.
What do you want?
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/16553#comment:66>
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.
