#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 nthiery):

 Replying to [comment:455 SimonKing]:
 > Replying to [comment:454 nthiery]:
 > > Pushed on u/nthiery/ticket/10963
 >
 > How does it relate with the branch that is attached to this ticket? Does
 the attached branch contain commits that are not in your branch (e.g., my
 commit to make the lazy imports even safer, by using as_name)?

 I branched off right before that commit; actually that commit is the
 single reason for my branching off: since it was still to be
 discussed, I did not want to merge it right away in my changes, but I
 did not want it either to look like I was discarding it by having the
 ticket branch not contain that commit.

 Cons for the commit: it's imposing a bit more redundant information on
 the developer in many spots when there is an alternative three lines
 localized robust fix (no risk of forgetting a spot).

 Pros for the commit: the developer might get used of not having to
 specify as_name for similar lazy imported nested classes, and get
 surprised in a different context.

 My personal preference is without the commit.

 > At some point, the work branch should be attached to the ticket, I
 suppose.

 Definitely!

 Cheers,
                                Nicolas

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