psychology dector

TC39 [1] is the committe that currently plans ECMAScript 6 (code-named ECMAScript.next), the next version of the JavaScript language standard. In this blog post, I’m summarizing the highlights of several meetings that they had in 2013, in March, May, July, September and November. Previous blog posts summarized prior meetings. This post is made possible by Rick Waldron’s excellent notes of the meetings. March Adobe joins TC39 ( announcement ). Iterator protocol: TC39 decided on an iteration protocol for ECMAScript 6, which is described in [2] . new Date(dateObj) creates a clone of dateObj . Two new array methods proposed by Rick Waldron: Array.prototype.find(predicate, thisArg?) Array.prototype.findIndex(predicate, thisArg?) May (All highlights subsumed by more recent explanations below.) July Maps can optionally be initialized via an iterable [2] of [key,value] pairs. Two new arra...

TC39 [1] is the committe that currently plans ECMAScript 6 (code-named ECMAScript.next), the next version of the JavaScript language standard. January 29–31, they had another meeting. Thanks to Rick Waldron’s notes , we can read up on what has been decided. This blog post describes the highlights. Previous blog posts summarized prior meetings. (Note: a blog post on the March TC39 meeting will be posted at some time in the future.) January 29 Object.is() : strict equality ( === ) is safer than sloppy equality ( == ). But it still has the quirk of NaN not being equal to itself [2] . The original plan for ECMAScript 6 was to introduce an is operator that fixes this quirk, but those plans have been abandoned. Instead, you can use Object.is(op1, op2) if you need “stricter” equality [2] . Object.is() also distinguishes positive and negative zero [3] (which isn’t always desirable). ECMAScript Internationalization API (ECMA-402): Chrome 24 shipped with an (unprefixed) imp...

From November 27-29, 2012, the Ecma Technical Committee 39 (TC39, [1] ) had another meeting, where decisions were made about ECMAScript.next (the code name for ECMAScript 6 [1] ). This blog post summarizes and explains the highlights. It is based on Rick Waldrons excellent notes that he put up on GitHub. There is also a list of all 2ality posts on TC39 meetings. November 27 TC39 approved the final draft of the Internationalization API (ECMA-402). Since then, on December 12, the Ecma General Assembly unanimously approved ECMA-402, making it a standard . The API exists separately from ECMAScript and can be used under ECMAScript 5 or later. Plans for version 2.0 are currently being made. High-priority functionality includes case conversion and message formatting that can handle things such as gender and grammatical number. Alex Slexton has experience with message formatting [2] and will be consulted. String.prototype.normalize() : Sometimes several Unicode code points repre...

Thanks to Rick Waldron , we have a detailed account of the decisions regarding ECMAScript.next that were made by TC39 [1] during its meeting from September 18-20, 2012. This blog post summarizes and explains the highlights. September 18 Highlights of the notes : The final draft of the Internationalization API (ECMA-402) has been approved ( page with PDFs , HTML format ). It will be submitted to the Ecma General Assembly for ratification. This API exists separately from ECMAScript and will be available for ECMAScript 5 or later. TC39 discussed River Trail [2] , JavaScript language extensions for parallel programming. River Trail won’t be in ECMAScript 6, but ECMAScript 7 or later is possible. For a while, operators for batch-assignment and/or batch-definition were considered for inclusion in ECMAScript 6. The latest decision was to instead use a function and to specify the properties to be added via an object literal. This kind of merging of two objects is ...