#16340: Infrastructure for modelling full subcategories
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner:
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-6.4
Component: categories | Resolution:
Keywords: full | Merged in:
subcategories, homset | Reviewers: Darij Grinberg,
Authors: Nicolas M. Thiéry | Travis Scrimshaw, Simon King
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/categories/full_subcategories-16340|
eb621c7beacb797f43fd41c9156edc453e80a902
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by SimonKing):
* status: needs_review => positive_review
Comment:
Hm. I did not find the category primer very helpful, as it only gives an
example (cartesian product) on objects. But it does not tell what actually
happens to the categories, and it does not tell how it is defined, nor how
it is implemented. I somehow recall from reviewing it how it was
implemented, but I would not easily be able to provide a mathematical
definition.
Anyway. The new code that we are discussing here seems good to me.
--
Ticket URL: <http://trac.sagemath.org/ticket/16340#comment:62>
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.
