Message298257
This seems like it optimizes an irrelevant use case, comparing a container to itself.
I don't think this is likely to benefit any existing code, so it would be better not to add more code clutter/complexity with another special case code path unless we're pretty sure that special case actually arises in practice.
FWIW, the note about identity-implies-equality is a statement about how containers implement element comparison rather than about how two containers are compared to one another (as implemented in PyObject_RichCompareBool()). Also, it isn't just an optimization, it is necessary to help us reason about containers (i.e. preserving the invariant: all(x in c for x in c)). |
|
Date |
User |
Action |
Args |
2017-07-13 04:58:33 | rhettinger | set | recipients:
+ rhettinger, wbolster |
2017-07-13 04:58:33 | rhettinger | set | messageid: <1499921913.4.0.933851064383.issue30907@psf.upfronthosting.co.za> |
2017-07-13 04:58:33 | rhettinger | link | issue30907 messages |
2017-07-13 04:58:32 | rhettinger | create | |
|