Unicode support in new ES6 spec draft

Mark Davis ☕ mark at macchiato.com
Mon Jul 16 14:57:50 PDT 2012


In order to support backwards iteration (which is sometimes used), we
should have codePointBefore.

------------------------------
Mark <https://plus.google.com/114199149796022210033>
*
*
*— Il meglio è l’inimico del bene —*
**



On Mon, Jul 16, 2012 at 2:54 PM, Gillam, Richard <gillam at lab126.com> wrote:

> Why is it intentional?  I don't see the value in restricting it.  You've
> mentioned you're optimizing for the forward-iteration case and want to have
> a separate API for the backward-iteration case.  What about the
> random-access case?  Is there no such case?  Worse, it seems like if you
> use this API for backward iteration or random access, you don't get an
> error; you just get *the wrong answer*, and that seems dangerous.  [I guess
> the "wrong answer" is an unpaired surrogate value, which would tip the
> caller off that he's doing something wrong, but that still seems like extra
> code he'd need to write.]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120716/b28ce7bd/attachment-0001.html>


More information about the es-discuss mailing list