I think we could go either way. It depends on the usage mode. 1. The case where performance is crucial is where you are comparing gazillions of strings, such as records in a database. 2. If the number of strings to be compared is relatively small, and/or there is enough overhead anyway, the performance win by turning off full normalization would be lost in the noise.
So if #2 is the expected use case, we could require full normalization. Mark <https://plus.google.com/114199149796022210033> * * *— Il meglio è l’inimico del bene —* ** On Fri, Aug 31, 2012 at 9:56 AM, Norbert Lindenberg < ecmascr...@norbertlindenberg.com> wrote: > The question for ECMAScript then is whether we should stick with "must do" > (the current state of the specifications) or change to "must be able to do". > > The changes for "must be able to do" would be: > > - In the Language specification, remove the description of > String.prototype.localeCompare, and require implementations to follow the > Internationalization API specification at least for this method, or better > provide the complete Internationalization API. That way, localeCompare > acquires support for the normalization property in options, and the -kk- > key in the Unicode locale extensions. >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
