Message77374
| Author | pitrou |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, brett.cannon, christian.heimes, georg.brandl, lemburg, mark.dickinson, pitrou, rhettinger |
| Date | 2008-12-08.23:58:53 |
| SpamBayes Score | 0.00030993196 |
| Marked as misclassified | No |
| Message-id | <1228780732.27610.2.camel@localhost> |
| In-reply-to | <1228780369.41.0.499582675724.issue1717@psf.upfronthosting.co.za> |
| Content | |
|---|---|
I wrote: > IMO PyUnicode_Compare() should be replaced by a hypothetical > PyObject_RichCompare(), which allows to take shortcuts when comparing > strings of different length and a Py_EQ or Py_NE comparison is requested. ... and I didn't even remember that PyUnicode_RichCompare() already exists. So let my proposal be to enable those optimizations inside the existing PyUnicode_RichCompare(), and dump PyUnicode_Compare(). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-12-08 23:58:56 | pitrou | set | recipients: + pitrou, lemburg, brett.cannon, georg.brandl, rhettinger, amaury.forgeotdarc, mark.dickinson, christian.heimes, benjamin.peterson |
| 2008-12-08 23:58:53 | pitrou | link | issue1717 messages |
| 2008-12-08 23:58:53 | pitrou | create | |