このステージの詳細についてはThe TC39 Processを参照してください。 2ヶ月に1度行われるTC39のミーティングにおいて、プロポーザルごとにステージを進めるかどうかを議論します。 このミーティングの議事録もGitHub上のtc39/tc39-notesにて公開されています。 ステージ4となったプロポーザルはドラフト版であるtc39/ecma262へマージされます。 そして毎年の決まった時期にドラフト版を元にしてECMAScript 20XXとしてリリースします。 この仕様策定プロセスの変更は、ECMAScriptに含まれる機能の形にも影響しています。 たとえば、class構文の策定は最大限に最小のクラス(maximally minimal classes)と呼ばれる形で提案されています。 これによりES2015でclass構文が導入されましたが、クラスとして合意が取れる最低限の
Check out my book (free online): “Exploring ES2018 and ES2019”. Buy it now and get all future updates. The feature set of ECMAScript 2018 was finalized during the latest TC39 meeting (23-25 January 2018). This blog post describes it. A word on ECMAScript versions # Note that since the TC39 process was instituted, the importance of ECMAScript versions has much decreased. What really matters now is
This repository contains a proposal for adding an import.meta metaproperty to JavaScript, for holding host-specific metadata about the current module. It is currently in stage 4 of the TC39 process. Previously this problem space was discussed with the module-loading community in whatwg/html#1013. The result was a presentation at the May 2017 TC39 meeting of these slides. The committee's feedback a
The ECMAScript proposal “Shared memory and atomics” by Lars T. Hansen has reached stage 4 this week and will be part of ECMAScript 2017. It introduces a new constructor SharedArrayBuffer and a namespace object Atomics with helper functions. This blog post explains the details. Update 2017-02-24: Complete rewrite of Sect. 4, “Atomics: safely accessing shared data”. Parallelism vs. concurrency # Be
► 2026 (4) ► 03 (2) ► 02 (2) ► 2025 (7) ► 08 (2) ► 07 (1) ► 05 (1) ► 01 (3) ► 2024 (2) ► 09 (1) ► 08 (1) ► 2023 (7) ► 05 (1) ► 04 (1) ► 03 (4) ► 01 (1) ► 2022 (3) ► 12 (1) ► 06 (1) ► 05 (1) ► 2021 (9) ► 12 (1) ► 11 (1) ► 10 (1) ► 09 (1) ► 07 (1) ► 06 (1) ► 05 (3) ► 2020 (13) ► 12 (1) ► 11 (2) ► 10 (1) ► 09 (2) ► 08 (1) ► 06 (1) ► 04 (2) ► 03 (1) ► 02 (1) ► 01 (1) ► 2019 (1) ► 06 (1) ► 2018 (6) ► 1
Asynchronous APIs frequently need to provide the user with some way to cancel long running or expensive operations. Some examples: A browser HTTP fetch API needs to allow the user to cancel network operations if the current request is no longer required by the user interface. A database access API needs to allow the user to cancel a long-running query when the client no longer needs the results of
Decorators have three primary capabilities: They can replace the value that is being decorated with a matching value that has the same semantics. (e.g. a decorator can replace a method with another method, a field with another field, a class with another class, and so on). They can provide access to the value that is being decorated via accessor functions which they can then choose to share. They
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く