#19141: Poset documentation polishing: Boolean-valued properties
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: enhancement | Status: positive_review
Priority: minor | Milestone: sage-6.10
Component: combinatorics | Resolution:
Keywords: poset | Merged in:
Authors: Jori Mäntysalo | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/poset_documentation_polishing__boolean_valued_properties|
39d1e185906821d6fcece65560e1081eb11e1493
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jmantysalo):
Replying to [comment:24 vdelecroix]:
> You can have both
> {{{
> def is_chain(self, data=None):
> }}}
No! Please no!
They do very much different thing. Already `rank` gives me a headache, as
it can return a property of a poset (height, not depending if the poset is
ranked or not) or a a property of an element (rank in ranked poset).
...or at least this is how ''I'' see it. A poset is an abstract thing that
might have a property like width. Or it is a concrete thing where I can
ask for example if `a` is greater than `b`. But if ''majority'' sees it
other way, then of course I must accommodate to it.
--
Ticket URL: <http://trac.sagemath.org/ticket/19141#comment:25>
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.
