You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Due to the recent changes on freenode, TC39 has moved to Matrix as its communication platform of choice. Read more here. The TC39 meeting in May, one of the shorter two day meetings of the committee, primarily focused on more mature proposals, and no stage 1 proposals were introduced. Object.hasOwn moved forward quickly, reaching stage 3 at this meeting. In addition, Top-level await and RegExp Mat
There were several items on the agenda, this post focuses on feature proposals and their progress from the meeting that was held between 19-21st July 2022. Stage 4: Hashbang Grammar: match de-facto usage in some CLI JS hosts that allow for #! Shebangs / Hashbang. Stage 3: Duplicate named capturing groups: allow regex capturing group names to be repeated. Stage 2: Import Reflection: Proposal for sy
In all our pseudocode examples supposing a Japanese calendar thus far, we've been passing in era names as lowercased ASCII string identifiers made from English transliterations of the names, e.g. { year: 2, era: 'reiwa' } for the current year. That requires that these identifiers are unique. However, that seems not to be the case as there are several eras written with different kanji but with the
Currently, the spec sends mixed signals to programmers about the with statement; this PR attempts to clear up the ambiguity by adding text that explicitly discourages the use of the with statement in new ECMAScript code. This is an attempt to solve a specific problem: developers and technical writers are unclear about the status of the with statement. See this StackOverflow question or this discus
V8 JavaScriptエンジンを使用し、Rustによって構築されているJavaScript/TypeScriptランタイムであるDeno開発チームは、JavaScriptの定義を維持し進化させるTC39ワーキンググループへの参加を12月13日(現地時間)に発表した。 今回の、TC39ワーキンググループへの参加は、JavaScriptの次期イテレーションについて、他のECMAメンバーおよびより広範なJavaScriptコミュニティと協力することを目的としたもので、とりわけサーバサイドJavaScriptのユーザーに役立つ機能と言語の改善を推進していく。 間もなく取り組む予定の機能としては、ESモジュールグラフにおける非JavaScriptアセットのサポート向上、明示的なリソース管理のサポート向上、非同期反復のためのより広範な標準ライブラリ関数が挙げられるほか、TypeScriptがDen
Some TC39 delegates are organizing meetings with various stakeholders in order to get more input in the process and share information with the community. Current calls include: Educators - Monthly on second Thursday 12:00:00 GMT-0400 (Eastern Daylight Time) Tools and transpilers - Monthly on the fourth Wednesday 12:00:00 GMT-0400 (Eastern Daylight Time) ... Planned future calls include: Open-to-ev
Sorry it's too late to add this issue, I commented that on the yesterday meeting. Though I didn't want to block this proposal in the meeting, I think we still have chance to think about the alternative. The problems of splice, toSpliced There are many complaints about the old splice method in the community, the main issues of it are: Bad name: splice is a very uncommon word, as word usage frequenc
TC39でStage3となっているTemporalについて、使ってみるとそれぞれの変換周りが色々躓いたのでまとめる。 また、今回は@js-temporal/polyfillを利用している https://github.com/js-temporal/temporal-polyfill 今回の登場人物 Temporalについてはいくつかの種類があることを理解する必要がある。 今回はざっくりな説明に留めるので、詳細は下記を参照 Temporal.PlainDateTime Timezoneを持たない日付の状態 ユーザーに向けた表記などで利用しやすい。 同じ仲間にPlainDate,PlainTime,PlainYearMonth,PlainMonthDayがある Temporal.Instant Unixtimeのような、場所や環境によらない値 ZonedDateTimeにだけ変換可能 Tem
// binding patterns const Foo(y) = x; // instance-array destructuring const Foo([y]) = x; // nested array destructuring const Foo({y}) = x; // nested object destructuring const [Foo(y)] = x; // nesting const { z: Foo(y) } = x; // .. const Foo(Bar(y)) = x; // .. const X.Foo(y) = x; // qualified names (i.e., a.b.c) // assignment patterns Foo(y) = x; // instance-array destructuring Foo([y]) = x; // n
Structs are declarative sealed objects. There are two kinds of structs: unshared structs and shared structs. Unshared structs behave as if they were sealed objects. Shared structs have additional restrictions and can be concurrently accessed from different agents. Both unshared and shared structs have the following properties: Opaque storage like plain objects. Not aliasable via ArrayBuffer or Sha
ECMAScript string values are a finite ordered sequence of zero or more 16-bit unsigned integer values. However, ECMAScript does not place any restrictions or requirements on the integer values except that they must be 16-bit unsigned integers. In well-formed strings, each integer value in the sequence represents a single 16-bit code unit of UTF-16-encoded Unicode text. However, not all sequences o
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く