#14159: Don't install callbacks on values of TripleDict, MonoDict
------------------------------+---------------------------------------------
Reporter: nbruin | Owner: tbd
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.8
Component: memleak | Resolution:
Keywords: | Work issues: Make part the coverage script
happy
Report Upstream: N/A | Reviewers: Nils Bruin
Authors: Simon King | Merged in:
Dependencies: #13387 | Stopgaps:
------------------------------+---------------------------------------------
Comment (by SimonKing):
I am just thinking: Perhaps one should enrich the key of the
`KeyedReference`, so that it states ''where'' we are supposed to find the
reference that caused the callback. I am thinking of an additional int,
that is 1, 3 or 5 if the reference is in the first, second or third part
of the key (1,3,5 give the relative position in the bucket), and 6 if the
reference belongs to the value of the item.
In that way, we would avoid the racing condition I described in the
previous comment, *and* we would not need to create a separate class
`TripleDictEraserOnValue`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14159#comment:23>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
