This says that after relabeling a lattice we have a poset:
L=LatticePoset({0:[1]})
type(L.relabel(lambda n: n+1))
Should this be corrected at posets.py, or should lattices.py contain
wrapper functions? As a code perspective it seems logical to a class
derived from poset to define it's own function. On the user perspective
relabeling of a lattice is just a relabeling of a poset, it is kind of
"just the same thing". (Whereas, for example, subposet of a lattice is not
always a lattice.)
Or should we left it to user to say LatticePoset(L.relabel(...))?
--
Jori Mäntysalo
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
