[Python-Dev] Python semantic: Is it ok to replace not x == y with x != y? (no)
Nick Coghlan
ncoghlan at gmail.com
Wed Dec 16 01:01:14 EST 2015
More information about the Python-Dev mailing list
Wed Dec 16 01:01:14 EST 2015
- Previous message (by thread): [Python-Dev] Python semantic: Is it ok to replace not x == y with x != y? (no)
- Next message (by thread): [Python-Dev] Python semantic: Is it ok to replace not x == y with x != y? (no)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 15 December 2015 at 23:11, Victor Stinner <victor.stinner at gmail.com> wrote: > I guess that the optimizations on "in" and "is" operators are fine, > but optimizations on all other operations must be removed to not break > the Python semantic. Right, this is why we have functools.total_ordering as a class decorator to "fill in" the other comparison implementations based on the ones in the class body. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Python semantic: Is it ok to replace not x == y with x != y? (no)
- Next message (by thread): [Python-Dev] Python semantic: Is it ok to replace not x == y with x != y? (no)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list