#16340: Model full subcategories
-------------------------------------+-------------------------------------
       Reporter:  nthiery            |        Owner:
           Type:  enhancement        |       Status:  new
       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:                     |
-------------------------------------+-------------------------------------
Changes (by nthiery):

 * commit:   => 2f2d09bec3a2e77021670d996abe2dd399fc63ec


Comment:

 Replying to [comment:2 darij]:
 > Ideally, for every piece of algebraic structure there should be both a
 full and a fully structure-aware subcategory. So there should be a
 UnitalAlgebrasWithUnitalMorphisms and a
 UnitalAlgebrasWithArbitraryMorphisms, etc.; more importantly, there should
 be categories for graded modules with graded morphisms and with arbitrary
 morphisms (I don't remember out of the hat which is the one we have) and
 categories for modules-with-basis with basis-preserving morphisms and with
 arbitrary morphisms etc.

 Agreed.

 > This might not belong into this ticket, but please make sure that your
 model takes this into account and does not handle fullness as a hardcoded
 property of the relevant axiom / functorial construct.

 I guess that's alright: when we will want both, we will just need to
 have two distinct categories/axioms/functorial construction for the
 two situations. I am missing a good idiom / naming convention though.

 In the mean time, the current implementation makes a default choice on
 a case by case basis, according to the foreseen main use case for the
 category (see the doc).

 > Other than this I like the proposal!

 Cool. I just pushed a first attempt. It's probably reasonably
 complete. The main things that need discussion are:

 - Terminology and method names

 - Are there categories which need special handling that I missed?

 - The default choices I have made.

 Cheers,
                                    Nicolas
 ----
 Last 10 new commits:
 
||[http://git.sagemath.org/sage.git/commit/?id=54c3d67befc2a991380f86ce3cc0836899d97cb4
 54c3d67]||{{{#15801: Initialize the base ring for module homsets}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=aa0159142f58b1feb9f2462aec4cc24a806165b3
 aa01591]||{{{#15801: doctests for CategoryObjects.base_ring + docfix in
 Modules.SubcategoryMethods.base_ring}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=79f476698d8658ca8649ab765de00995c24f5455
 79f4766]||{{{Merge branch 'public/categories/over-a-base-ring-
 category-15801' of trac.sagemath.org:sage into public/categories/over-a
 -base-ring-category-15801}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=281f5392e81e98d835ddf249325e66c1c36a08cc
 281f539]||{{{Added back in import statement as per comment.}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=96c631f536a20733a80e74fba45fecd5d98f6fd5
 96c631f]||{{{Merge branch 'develop' into categories/axioms-10963}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=b1a2aede666273d01405811aad2c6338a06c0330
 b1a2aed]||{{{Trac 10963: two typo fixes to let the pdf documentation
 compile}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=c16f18b56c2b5470088bbcf110ddbb15be6caf0c
 c16f18b]||{{{Merge branch 'public/ticket/10963-doc-distributive' of
 trac.sagemath.org:sage into categories/axioms-10963}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=dcb11d850530d23e1d8867daa84ade0e04d7ce15
 dcb11d8]||{{{Merge branch 'categories/axioms-10963' into
 categories/over_a_base_category-15801}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=15658bd13f22b874423f62b8e6e6fb4d4f7b56ec
 15658bd]||{{{Trac 15801: fixed merge with #12630}}}||
 
||[http://git.sagemath.org/sage.git/commit/?id=2f2d09bec3a2e77021670d996abe2dd399fc63ec
 2f2d09b]||{{{16340: infrastructure for modelling full subcategories}}}||

--
Ticket URL: <http://trac.sagemath.org/ticket/16340#comment:5>
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.

Reply via email to