On Mon, Jun 15, 2015 at 12:07 AM, 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote:
> Hi there! > > I would like to understand the (intended) purpose of the three classes > Map, Morphism and PoorManMap. > > What I know so far: > > * Morphism inherits from Map, and provides a few more methods, in > particular category, is_endomorphism, is_identity. > > * Map itself is used only in very few places, it appears to play a > somewhat "internal" role. > > * Map, Morphism and PoorManMap all assume that the map can be applied to > elements. However, PoorManMap does not assume that domain and codomain are > parents. > > My main question is why Map and Morphism are separate classes and whether > it would make sense to have a more basic class, eg "CategoryMorphism", > which provides composition of abstract morphisms between CategoryObjects. > Seems reasonable, if we actually have some examples to implement of CategoryObject which are not parents, where we can do nontrivial compositions of the morphisms. David > > Martin > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
