#15456: fix bug in has_right/left_descents in Weyl group code
---------------------------------+-------------------------
       Reporter:  zabrocki       |        Owner:
           Type:  defect         |       Status:  new
       Priority:  major          |    Milestone:  sage-5.13
      Component:  combinatorics  |   Resolution:
       Keywords:                 |    Merged in:
        Authors:                 |    Reviewers:
Report Upstream:  N/A            |  Work issues:
         Branch:                 |       Commit:
   Dependencies:                 |     Stopgaps:
---------------------------------+-------------------------

Comment (by zabrocki):

 I take the part about it being correct in `CoxeterGroup` back.  It seems
 to only be correct for the `CoxeterGroups().example()`.

 I assume that you are right in that "Coxeter group category provides a
 default implementation for the other" but no one has implemented
 `has_right_descent` or `has_left_descent` for any of the finite or affine
 `WeylGroups` or `CoxeterGroups` (to an end user of these groups, this is a
 bug because it should just raise a `Not Implemented` error).

 Is the correct solution then that

 (1) someone needs to implement them for each of the types

 (2) that the default implementation should be `has_right_descent` should
 call `has_descent(self, side=right)`

 (3) the default implementation of `has_right_descent` should raise a `Not
 Implemented` error

 (4) something else?

--
Ticket URL: <http://trac.sagemath.org/ticket/15456#comment:5>
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/groups/opt_out.

Reply via email to