#14058: Weakly reference binary operation codomains
-----------------------------------+----------------------------------------
Reporter: robertwb | Owner: rlm
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.7
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Robert Bradshaw | Merged in:
Dependencies: #12313 | Stopgaps:
-----------------------------------+----------------------------------------
Comment (by SimonKing):
I think it makes sense to ask
[https://groups.google.com/forum/?fromgroups=#!topic/sage-
devel/7FCHou9nkIg sage-devel] whether it is better to fix this leak or
not.
I believe that keeping A and B alive should prevent C from garbage
collection. In contrast, keeping C alive should ''not'' prevent A and B
from garbage collection. Currently, it is the other way around. Perhaps we
should try to think through whether having a weak reference to the domain
of coercion or conversion maps would work.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14058#comment:20>
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.