#12630: Add representations of quivers and quiver algebras to sage
-------------------------------------+-------------------------------------
Reporter: JStarx | Owner: AlexGhitza
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.2
Component: algebra | Resolution:
Keywords: algebra, quiver, | Merged in:
module, days49 | Reviewers: Simon King
Authors: Jim Stark, Simon | Work issues: mutability of quiver
King, Mathieu Guay-Paquet, Aladin | representation elements
Virmaux | Commit:
Report Upstream: N/A | b2248e0da6dcd8b6c07ff91db00491ce673576e8
Branch: | Stopgaps:
public/combinat/quivers |
Dependencies: #12412, #12413, |
#14806, #15491, #15623, #15810 |
-------------------------------------+-------------------------------------
Changes (by SimonKing):
* status: needs_review => needs_work
* work_issues: => mutability of quiver representation elements
Comment:
I think it is a accepted standard in Sage that `zero()` and `one()` are
cached. And of course, cached elements should be immutable.
I see two ways to proceed. Either we replace `set_element()` by
`_set_element()`, or we let `QuiverRepElement` inherit from
sage.structure.mutability.Mutability, and try to see if we can afford to
let it be immutable by default. I'll try the latter first.
That said, I suppose we could completely remove the `set_element` method:
It is not used, except in doctests.
--
Ticket URL: <http://trac.sagemath.org/ticket/12630#comment:236>
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.
