#16509: bug in .as_finite_field_element() when minimal=True
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: finite rings | Resolution:
Keywords: bug | Merged in:
Authors: Peter Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/pbruin/16509-as_finite_field_element|
5572837f991d5ed6a1674e009de8c38e0c3bbc7c
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:7 pbruin]:
> Replying to [comment:5 vdelecroix]:
> I don't think we should change the internal representation when the user
calls `as_number_field_element()`. Currently, two elements that compare
equal can have a different hash (which is a bad thing); changing the
internal representation of an element would therefore mean that its hash
can change, which is even worse.
right
> QQbar is careful enough to ensure that equal elements with different
representations have the same hash; it would be nice if we could somehow
do that too.
I know but they "cheat" using the fact that you have a natural embedding
to the complex field. Do you have an idea to get a (fast) coherent hash
for algebraic closure elements?
--
Ticket URL: <http://trac.sagemath.org/ticket/16509#comment:8>
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.
