#15862: Mutability of tableaux, for the n-th time
-------------------------------------------------+-------------------------
Reporter: darij | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.2
Component: combinatorics | Resolution:
Keywords: tableaux, sage-combinat, | Merged in:
mutability | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Comment (by darij):
@Nicolas: Thank you. Can you remind me how `ClonableList` differs from
`CombinatorialObject`? Does it allow mutation at clone time?
Currently tableaux can have non-integer entries, and this is both useful
and used (e.g. for skew tableaux). So I'm not convinced of switching to C
ints.
@Travis: Apparently combinatorial objects hash like this:
{{{
if self._hash is None:
self._hash = str(self._list).__hash__()
return self._hash
}}}
So the `__repr__` is not used, but rather the list is taken into a string
and the latter is hashed. I assume this won't take any longer with tuples?
Or am I looking at the wrong hash function?
Thanks also for your comments on #14711, though they're still somewhat
over my head. What morphisms hold a weak reference to `Tableaux()`?
--
Ticket URL: <http://trac.sagemath.org/ticket/15862#comment:8>
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.