Opened 9 years ago
Closed 3 years ago
#10130 closed enhancement (wontfix)
Revamp __hash__, __cmp__ and __richcmp__
Reported by: | roed | Owned by: | robertwb |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | coercion | Keywords: | |
Cc: | robertwb, nthiery | Merged in: | |
Authors: | Reviewers: | Jeroen Demeyer | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
There are a number of confusing and non-optimal features of the way Sage currently handles hashing and comparison.
- Because of Python, if you override one of these functions, you must redefine the others as well. This is easy to forget and confuses new users. For Cython classes, this can be fixed in #18329.
- hashes of parents are used extensively in the coercion framework, so speed is quite important. But since parents are usually written in Python, the current model will always have at least a dictionary lookup (for example, in finding a cached
self.__hash
). And often parents don't override the default hashing code and they fall back to slow__repr__
methods. Fixed by #715???
Attachments (1)
Change History (17)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
Also, in Python 2.6, you can set A.hash = None, to indicate that an object is not hashable. We should probably do this for the various immutable types in Sage, rather than raising a type error. I don't know if this works currently (I can't do it from the command line on a mutable matrix for example).
comment:3 Changed 9 years ago by
As an example of the speed gains possible, this patch resolves #9886.
comment:4 Changed 9 years ago by
Just a quick note: for parents that use UniqueRepresentation?, the hash is given by the id of the object; one can't be much faster (except that UniqueRepresentation? is not Cython'ed yet):
F = CombinatorialFreeModule(QQ,QQ) sage: F.__hash__() 98169392 sage: id(F) 98169392
Other than that, I am all for improvements in this direction, because at this stage I am still confused about what I should do when I want to implement a partially ordered set in Python. Besides it would be best if it was possible to implement such partial orders in categories (remember that element methods defined in categories are overridden by methods defined in concrete classes like Element).
comment:5 Changed 7 years ago by
- Cc nthiery added
Nicolas T. and I somewhat came across the second point in working on #13605. In particular, I have changed Partition
to inherit from Element
, use the rich comparisons, and removed the __cmp__()
method. Thus calling things like
sage: sorted(Partitions(5), cmp)
raise the "BUG - comparsion not implemented" exception. This holds for any subclass of Element
which does not implement a __cmp__()
and does not fall back on the rich comparisons as regular python objects would.
comment:6 Changed 6 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:7 Changed 6 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:8 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:9 Changed 5 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:10 Changed 5 years ago by
Related: #17890.
comment:11 Changed 5 years ago by
comment:12 Changed 5 years ago by
- Description modified (diff)
comment:13 Changed 5 years ago by
- Description modified (diff)
comment:14 Changed 4 years ago by
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Reviewers set to Jeroen Demeyer
- Status changed from new to needs_review
This is a too general ticket. And most of this is actually fixed.
comment:15 Changed 4 years ago by
- Status changed from needs_review to positive_review
comment:16 Changed 3 years ago by
- Resolution set to wontfix
- Status changed from positive_review to closed
Determined to be invalid/duplicate/wontfix (closing as "wontfix" as a catch-all resolution).
I don't know the best way to resolve these issues, but here are some ideas.
_hash_
,_cmp_
and_richcmp_
that users will override.__hash
". I don't know if this should be set to self._hash_() during the parent's__init__
method, or set to -1 and then reset upon the first call to__hash__
.SageObject
, have the default behavior of_hash_()
be to returnhash(repr(self))
. For parents, have the default value of hash depend onself.construction()
?_richcmp_
. By default, have_richcmp_
determined by a total ordering implemented by_cmp_
. So if you want to have partial ordering, or a different partial and total ordering, you need to implement both_cmp_
and_richcmp_
._cmp_
checks first for pointer equality. If non-equal, it compares the hashes. If those are nonequal, returns the cmp of the hashes. Otherwise, returns the cmp of the pointers._cmp_
, but would instead raise an error.