#19302: Stopgap for Element.__hash__
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.9
defect | Resolution:
Priority: | Merged in:
blocker | Reviewers:
Component: misc | Work issues:
Keywords: | Commit:
Authors: | bf004c2def5615b5bfe96338911d00d24f0119ac
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
public/19302 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by nbruin):
Replying to [comment:6 ncohen]:
> Well, it pops out absolutely everywhere because this bug is very very
bad, and can generate wrong results absolutely everywhere.
No, it still needs a confluence of circumstances. It only leads to
possibly wrong results for elements where elements that are considered
equal can have different string representations. That can happen because
generators get renamed (an operation that shouldn't be supported in sage)
or because elements are not printed in a canonical form (either because
such a form isn't attainable or because it's expensive to attain). There
aren't that many parents in sage with that property (and we'll probably
have to disallow hashing there). It's worth fixing, but you don't have to
overstate the impact.
--
Ticket URL: <http://trac.sagemath.org/ticket/19302#comment:7>
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.
