Disposable is leaky by default · Issue #159 · tc39/proposal-explicit-resource-management
I'm a bit uneasy with the fact that it's allowed to create a Disposable without registering its dispose method to some kind of disposal scope, either with using on the current scope, or add to some DisposableStack. In fact, the disposal registration is opt-in, not opt-out. This gives a Disposable object leaky behavior by default. It's like still doing malloc() and free(), but added opt-in support
JavaScript naming conflicts: How existing code can force proposed features to be renamed
JavaScript naming conflicts: How existing code can force proposed features to be renamed Sometimes the name of a proposed feature (a method, a global variable, etc.) clashes with existing code and has to be changed. This blog post explains how that can happen and lists features that were renamed. Evolving JavaScript: Don’t break the web! # One core principle for evolving JavaScript is to not “bre
Official name bikeshed · Issue #321 · tc39/proposal-shadowrealm
With Realms at Stage 3, let's have an earnest bikeshedding discussion on the name "Realm". We've talked about renaming it many times in the past but AFAICT never had the earnest discussion. The shape of the current proposal has deviated sufficiently from long-standing uses of "Realm" in ecma262 and HTML that a different name seems more appropriate. At the July TC39, we have consensus that the majo
Editorial: disambiguate `with` statement's status by ddbeck · Pull Request #2441 · tc39/ecma262
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
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
CollectionCreateFrrom doesn't need the array-like alternative · Issue #3 · tc39/proposal-setmap-offrom
Editorial: Describe changes in ES2024 by bakkot · Pull Request #3282 · tc39/ecma262
Default constructor for Promise statics · Issue #544 · tc39/ecma262
esnext/es6-module-transpiler
Leverage ECMAScript Explicit Resource Management · Issue #256 · rust-diplomat/diplomat
Issue · tc39/proposal-array-grouping
CSS and JSON module scripts and CSP · Issue #7233 · whatwg/html
allow escape for more characters in u not just v? · Issue #27 · tc39/proposal-regexp-v-flag
Support for auto-accessor fields from the Stage 3 Decorators proposal by rbuckton · Pull Request #49705 · microsoft/TypeScript
Clarify security story. by letitz · Pull Request #378 · tc39/proposal-shadowrealm
Private members break proxies · Issue #106 · tc39/proposal-class-fields
Promise.prototype.finally should use onFinally's realm for newly creating functions · Issue #2222 · tc39/ecma262
data: / blob: URL mapping · Issue #166 · WICG/import-maps
Web compatibility issue in bricklink.com with "at" method name · Issue #41 · tc39/proposal-relative-indexing-method
Normative: Fix extending null by devsnek · Pull Request #1321 · tc39/ecma262
Editorial: Remove 'designed to be subclassable' by ptomato · Pull Request #2360 · tc39/ecma262