#10527: Implementation of quiver mutation type
-----------------------------------------------+----------------------------
Reporter: stumpc5 | Owner: sage-combinat
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.3
Component: combinatorics | Resolution:
Keywords: quiver mutation type days38 | Work issues:
Report Upstream: N/A | Reviewers: Hugh Thomas
Authors: Christian Stump | Merged in:
Dependencies: | Stopgaps:
-----------------------------------------------+----------------------------
Comment (by hthomas):
Gregg, I've looked at #10538, so now I think I understand what the point
of the elliptics code you introduced was (i.e., it wasn't actually
supposed to change the !QuiverMutationType at all, so, as I remarked, the
code you introduced would never actually be used when called by any
routine introduced by this patch), but I think it's a confusing way to
code it.
If you want, you could define some private method which both
!ClusterQuiver and !QuiverMutationType would call. Or, and maybe this
makes even more sense, !QuiverMutationType could call !ClusterQuiver to
build the quiver, but !ClusterQuiver would know how to build other quivers
that aren't the default quivers associated to any !QuiverMutationType.
In either of these cases, I would leave things as they are on this ticket,
and make the change of #10538.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10527#comment:119>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
