#16855: Make finite fields satisfy comparison by identity
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-6.4
Component: finite rings | Resolution:
Keywords: finite field | Merged in:
comparison | Reviewers:
Authors: Peter Bruin | Work issues:
Report Upstream: N/A | Commit:
Branch: | e1380c03931414a7f9715e936d587976f06807a2
u/pbruin/16855-FiniteField_comparison| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by nbruin):
Replying to [comment:4 jpflori]:
> Do we want coercions anyway?
> Wouldn't conversions be enough?
There is certainly a mechanism in place for caching conversions (as maps)
that would lead to exactly the same memory leak. A coercion in one
direction combined with a conversion in the other could lead to the same
leak.
It may be that there are ways to have a conversion and *not* a cached map.
In any case, however these things get solved, it's worth convincing
yourself that no memory leak has been created via the usual test:
{{{
for p in primerange(<large>):
<create fields with p>
<exercise them (add, multiply, build polynomial rings over them)>
gc.collect()
}}}
and ensure that there is not a large number of finite fields still in
memory (or just watch if memory consumption spirals out of control)
--
Ticket URL: <http://trac.sagemath.org/ticket/16855#comment:10>
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.
