On `String.prototype.codePointAt` and `String.fromCodePoint`
allen at wirfs-brock.com
Wed Sep 25 09:47:40 PDT 2013
On Sep 24, 2013, at 9:59 PM, Erik Arvidsson wrote:
> My concern is similar to Anne's. codePointAt will most likely not give
> the right behavior and I'm concerned adding this without working
> raising the bar significantly.
> Since this is already implementable in ES3 I don't see why we should rush this?
> I think we should apply the post ES6 process to this. Let's ship it
> when we feel confident that we got this right.
codePointAt is part of a larger comprehensive proposal  and was discussed in the context of that proposal at the March 2012 TC39 meeting . There isn't a lot of detail in the notes but I'm pretty sure we talked about why the proposed definition of codePointAt makes sense. We changed several things about the proposal at that meeting, but not codePointAt. I don't see anything new in this thread that should cause us to revisit the consensus we already have.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss