サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
中東情勢
ecmascript-daily.github.io
The changes of proposal’s status @ 98th meeting of Ecma TC39 ECMA-262 New Proposals Proposal Stage Stable Formatting 1 Locale Extensions 1 Iterator Sequencing 1 Joint Iteration 1 Negated in and instanceof operators 1 Updated Proposals Proposal From To RegExp.escape 1 2 Resizable and growable ArrayBuffers 3 4 ECMA-402 New Proposals No Data Updated Proposals No Data This diff is generated by ECMAScr
The changes of proposal’s status @ 78th meeting of Ecma TC39 New Proposals Proposal Stage
The changes of proposal’s status @ 70th meeting of Ecma TC39 New Proposals None Updated Proposals Proposal From To
The changes of proposal’s status @ 69th meeting of Ecma TC39 New Proposals Proposal Stage
The changes of proposal’s status @ 67th meeting of Ecma TC39. This TC39 meeting freeze ECMAScript 2019 features. See also proposals/finished-proposals.md at master · tc39/proposals ECMAScript 2019: the final feature set New Proposals Proposal Stage
The changes of proposal’s status @ 64th meeting of Ecma TC39. New Proposals Proposal Stage
The changes of proposal’s status @ 62nd meeting of Ecma TC39 New Proposals Proposal Stage
Notes Class Static Fields (Public & Private): 3 to 2. Class fields and private methods will be merged, and split. Class instance fields (public and private), and private instance methods are now one proposal, and at Stage 3. Class static fields (public and private), and private static methods are now a second proposal, and at Stage 2. – https://github.com/babel/proposals/issues/34#issuecomment-348
The changes of proposal’s status @ 59th meeting of Ecma TC39. Proposal Stage
Other proposals: tc39/proposals: Tracking ECMAScript Proposals Other changes: Add instructions for onboarding existing proposals When is the repository of proposal transferd to TC39 org? Previous ECMAScript proposal updates @ 2016-07
Statement Brian Terlson who is editor of ECMAScript said that Speaking as someone who proposed types for JavaScript in 2014: I do not believe types are in the cards for the near future. This is an extremely complex problem to get right from a standards perspective. Just adopting TypeScript as the standard would of course be great for TypeScript users, but there are other typed JS supersets with pr
Provide daily news about ECMAScript Next
このページを最初にブックマークしてみませんか?
『ECMAScript Daily』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く