Patches implementing `String.prototype.codePointAt` and `String.fromCodePoint` are available for both SpiderMonkey (https://bugzilla.mozilla.org/show_bug.cgi?id=918879) and V8 (https://code.google.com/p/v8/issues/detail?id=2840).

One spec bug remains to be fixed, though: <https://bugs.ecmascript.org/show_bug.cgi?id=1153>. It seems pretty clear the intent is to return `undefined` and not `NaN` (the algorithms in both the proposal and the ES6 draft agree on it), but it would be good to have this confirmed.

Is it a good idea for engines to start implementing these methods, or is their design still being discussed? The definitions of these methods have been in the ES6 draft for a long time (since July 2012) without any changes. Does that indicate stability? How sure are we that they will end up in the final ES6 spec?

Mathias  
http://mathiasbynens.be/

Patches implementing `String.prototype.codePointAt` and `String.fromCodePoint` are available for both SpiderMonkey (https://bugzilla.mozilla.org/show_bug.cgi?id=918879) and V8 (https://code.google.com/p/v8/issues/detail?id=2840).

One spec bug remains to be fixed, though: <https://bugs.ecmascript.org/show_bug.cgi?id=1153>. It seems pretty clear the intent is to return `undefined` and not `NaN` (the algorithms in both the proposal and the ES6 draft agree on it), but it would be good to have this confirmed.

Is it a good idea for engines to start implementing these methods, or is their design still being discussed? The definitions of these methods have been in the ES6 draft for a long time (since July 2012) without any changes. Does that indicate stability? How sure are we that they will end up in the final ES6 spec?