#13387: Improve MonoDict and TripleDict data structures
----------------------------------+-----------------------------------------
Reporter: nbruin | Owner: Nils Bruin
Type: enhancement | Status: needs_review
Priority: major | Milestone:
sage-duplicate/invalid/wontfix
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Nils Bruin | Merged in:
Dependencies: #11521, #12313 | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by nbruin):
Replying to [comment:5 SimonKing]:
> I see a logistic problem: The aim of #13904 is to fix some problems
introduced with #715. It should be a quick solution, since otherwise #715
will be unmerged. However, the ticket here also depends on #12313, which
has a positive review, but isn't merged yet. So, that's too slow.
>
> Therefore, I suggest that #13904 shall use the ideas from here, but
''only'' applied to `TripleDict`, so that #715 can remain in Sage.
>
> I think it is worth while to provide the `IdKeyDict` code in its full
generality (that's an attachment I made in #12313), but I am not sure,
perhaps that's for a different ticket. Then, #12313 should be tackled, and
probably again done as in `IdKeyDict` (but perhaps with specialised code).
>
> In other words: I suggest to split this ticket (one part done in #13904
ASAP, the other part later in #12313), so that this ticket shall be marked
as a duplicate.
>
> Do you agree?
There is nothing ''wrong'' with `TripleDict`, except for an eraser problem
we don't know how to fix. We should solve that for now by forbidding the
problematic keys in the documentation. In other words: "Don't use
`TripleDict` unless you know what you're doing". Then `TripleDict` doesn't
have any known bugs and we can take our time to think about how to make
`TripleDict` more generally applicable. Memory management, deallocation,
and weakref callbacks are genuinely hard ...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13387#comment:6>
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.
