#14711: Memleak when creating QuadraticField
-------------------------------------------------+-------------------------
Reporter: jpflori | Owner:
Type: defect | davidloeffler
Priority: critical | Status: new
Component: number fields | Milestone: sage-5.12
Keywords: memleak, number field, | Resolution:
QuadraticField | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: u/SimonKing/ticket/14711 | Commit:
Dependencies: | Stopgaps:
-------------------------------------------------+-------------------------
Comment (by SimonKing):
PS: It might be doable to guess from the construction of an object whether
it will be immortal or not, and then decide whether we store the coercion
in the domain or in the codomain. But note that this may slow down the
whole coercion system, because when searching a coercion it would always
be needed to look both at the domain and the codomain: Two searches where
we currently have only one.
And when the construction shall guide us what to do, then we always need
to compute the construction first---and actually not all parents are
currently provided with a construction.
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:35>
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.
