#16340: Infrastructure for modelling full subcategories
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: sage-6.4
Component: categories | Resolution: fixed
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:
eb621c7beacb797f43fd41c9156edc453e80a902| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:67 ncohen]:
> Hmmmmm... Then perhaps only a flag when this infrastructure is
initialized ? Doesn't matter much I guess, I it just unpleasant to see the
same (empty) function being copy/pasted one thousand times.
Or an attribute `_adds_structure`, and then define something like the
following:
{{{
#!python
def additional_structure(self):
if getattr(self._adds_structure, None):
return self
}}}
In that way, the method `additional_structure` would be defined only in
three places (default for categories, for categories with axiom, and for
functorial constructions), and non-default behaviour could be requested
more light-weight.
Nicolas, what do you think?
What do you think about it,
--
Ticket URL: <http://trac.sagemath.org/ticket/16340#comment:68>
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.
