This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients eric.snow, lemburg, pitrou, serhiy.storchaka, vstinner
Date 2013-04-07.17:31:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365355917.61.0.50166510912.issue17628@psf.upfronthosting.co.za>
In-reply-to
Content
Note that unicode_eq() always called after identity check and hash check. I.e. identity check in Victor's patch is redundant and unicode_eq() called only for strings which have the same hash. The probability to have the same first byte and be equal is a great.

unicode_compare_eq() and unicode_eq() are designed for different purposes. They cannot be just merged.

As the optimization for unicode_eq(), I would have suggested a checking of first machine words instead of first bytes, but this trick is too dirty.
History
Date User Action Args
2013-04-07 17:31:57serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, pitrou, vstinner, eric.snow
2013-04-07 17:31:57serhiy.storchakasetmessageid: <1365355917.61.0.50166510912.issue17628@psf.upfronthosting.co.za>
2013-04-07 17:31:57serhiy.storchakalinkissue17628 messages
2013-04-07 17:31:57serhiy.storchakacreate