On 8 November 2013 09:18, Laurence Tratt <lau...@tratt.net> wrote: > Looking up floats and longs is > now much faster; for many other types (e.g. strings or user objects whose > class does not override __eq__) these return immediately.
I wonder a bit if it is worth introducing additional fast paths for clearly nonsense (eg, string) cases, when it's the sensible case (user-provided types that provide __eq__) that we should be optimising for. Did you menchbark the code without such cases? -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely may reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to deny you those rights would be illegal without prior contractual agreement. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
