#17216: Poset / LatticePoset: [meet|join]matrix algorithm
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.4
Component: combinatorics | Resolution:
Keywords: | Merged in:
Authors: Jori Mäntysalo | Reviewers: Nathann Cohen
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/poset___latticeposet___meet_join_matrix_algorithm|
a649be931b249028ff1e5961fc948c2daf50c695
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ncohen):
> Actually, you can't remove that function from the category without
deprecating it.
If such an object exists somewhere in Sage when we should not move the
function from the category file to the lattice file, for that would be a
regression.
If such an object does not exist there is no reason to add a deprecation.
Bear in mind that an object that currently belong to the category of
`Lattices` and is not a `FiniteLattice` must implement its own
`is_meet_semilattice` and `is_join_semilattice`.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/17216#comment:15>
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.
