#10963: More functorial constructions
-------------------------------------+-------------------------------------
       Reporter:  nthiery            |        Owner:  stumpc5
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.1
      Component:  categories         |   Resolution:
       Keywords:  days54             |    Merged in:
        Authors:  Nicolas M. Thiéry  |    Reviewers:  Simon King, Frédéric
Report Upstream:  N/A                |  Chapoton
         Branch:                     |  Work issues:
  public/ticket/10963                |       Commit:
   Dependencies:  #11224, #8327,     |  eb7b486c6fecac296052f980788e15e2ad1b59e4
  #10193, #12895, #14516, #14722,    |     Stopgaps:
  #13589, #14471, #15069, #15094,    |
  #11688, #13394, #15150, #15506     |
-------------------------------------+-------------------------------------

Comment (by pbruin):

 Replying to [comment:465 nthiery]:
 > Replying to [comment:450 pbruin]:
 > > Maybe the quickest solution is to insert better-named aliases for
 these, rename the method `summands()` introduced here, and later deprecate
 `summand_projection()` and `summand_split()` in a different ticket.
 > >
 > > My first reflex would be to rename `summand_projection()` to
 `projection()` and `summand_split()` to `tuple()`.
 >
 > If you believe this is urgent enough to belong to #10963, then please
 > go ahead, and I'll review it.

 Not sure if 'urgent' is the right word, but it would be better to give
 method the right name from the start rather than using a less-than-ideal
 name for consistency with other less-than-ideal names...

 > To raise any confusion: I mean that if you construct a monoid M as a
 > cartesian product of other monoids, you would get a `M.factors()`
 > method which would have nothing to do with the concept of
 > factorization in the monoid M.

 I see.  How about
 {{{
 summand_projection() -> cartesian_projection()
 summand_split() -> cartesian_factors()
 summands() -> cartesian_factors()
 }}}
 In particular, the fact that the last two are equal would be nicely
 consistent with the fact that we already have `cartesian_product()` both
 for parents and for elements.

--
Ticket URL: <http://trac.sagemath.org/ticket/10963#comment:474>
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/groups/opt_out.

Reply via email to