#16340: Infrastructure for modelling full subcategories
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: categories | Resolution:
Keywords: full | Merged in:
subcategories, homset | Reviewers:
Authors: Nicolas M. ThiƩry | Work issues:
Report Upstream: N/A | Commit:
Branch: | 2f2d09bec3a2e77021670d996abe2dd399fc63ec
u/nthiery/categories/full- | Stopgaps:
subcategories-16340 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by nthiery):
Replying to [comment:10 SimonKing]:
> Or, even more informative: Return a pair `(op, method)`, such that
> - `op` is the operator (either as in `operator.contains`,
`operator.mul`, `operator.and`, or a parent/element method such as
`an_element`), and
> - `method` is an abstract parent/element method that has to be
implemented for `op` (i.e., `__contains__`, `_mul_`, or `_an_element`)
Possibly so indeed. Although this would be duplicating a bit the job
of `required_methods`. I am not sure we want to put a specific
emphasis on the methods related to an operation that adds structure
(e.g. '+') or that does not (e.g. '-').
Speaking of which: see #16363.
--
Ticket URL: <http://trac.sagemath.org/ticket/16340#comment:11>
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.