#16291: Fixing associativity of FormalCompositeMap
-------------------------------------+-------------------------------------
Reporter: sbesnier | Owner: sbesnier
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: categories | Resolution:
Keywords: associativity | Merged in:
FormalCompositeMap | Reviewers:
Authors: Sébastien Besnier | Work issues:
Report Upstream: N/A | Commit:
Branch: | 198085bda26743ebcb442f3b70698c3055395cd1
u/sbesnier/ticket/16291 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
Sorry for being annoying, but I'm afraid you partially misunderstood my
request about punctuation... By punctuation marks I meant one of `. , ; :
? !`, not equality signs or operators. (See the section "Whitespace in
Expressions and Statements" on the first linked page in comment:6.)
What is the reasoning behind `head()` and `tail()`? If you think of
morphisms as arrows, then composing two morphisms, say by putting `f`
first and `g` second, gives
{{{
f g
* ---> * ---> *
}}}
In this picture it would be visually suggestive to call `g` the head and
`f` the tail! Why not keep `first()` as it is, implementing a method
`last()` and making `second()` a deprecated alias for either `last()` or
`__getitem__(1)`?
--
Ticket URL: <http://trac.sagemath.org/ticket/16291#comment:8>
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.
