Intent to Ship: Explicit resource management (sync)

235 views
Skip to first unread message

Rezvan Mahdavi Hezaveh

unread,
Nov 21, 2024, 6:44:59 PMNov 21
to blink-dev

Contact emails

rez...@chromium.orgs...@chromium.org

Explainer

None

Specification

https://tc39.es/proposal-explicit-resource-management

Summary

This feature addresses a common pattern in software development regarding the lifetime and management of various resources (memory, I/O, etc.). This pattern generally includes the allocation of a resource and the ability to explicitly release critical resources.



Blink component

Blink>JavaScript>Language

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

No known interop or web compat risk.



Gecko: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1569081) This is a TC39 Stage 3 proposal.

WebKit: Positive (https://bugs.webkit.org/show_bug.cgi?id=248707) This is a TC39 Stage 3 proposal.

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Debuggability

We have added Devtools support for this proposal.



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes

https://github.com/tc39/test262/tree/05c45a4c430ab6fee3e0c7f0d47d8a30d8876a6d/test/staging/explicit-resource-management



Flag name on about://flags

None

Finch feature name

V8Flag_js_explicit_resource_management

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/42203506

Estimated milestones

Shipping on desktop133
DevTrial on desktop131


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5071680358842368?gate=5185990493995008

This intent message was generated by Chrome Platform Status.

Mike Taylor

unread,
Nov 21, 2024, 7:12:13 PMNov 21
to Rezvan Mahdavi Hezaveh, blink-dev

LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACJ3t%2Bh3WTkmGe%2B1irA1G%2Bcjz%2BKhAMay1jvDEY9%3DoRxfSNW7fw%40mail.gmail.com.

Chris Harrelson

unread,
Nov 27, 2024, 10:55:59 AMNov 27
to Mike Taylor, Rezvan Mahdavi Hezaveh, blink-dev

Rick Byers

unread,
Nov 27, 2024, 3:33:00 PMNov 27
to Chris Harrelson, Mike Taylor, Rezvan Mahdavi Hezaveh, blink-dev
FWIW, it looks like this is also covered by the same explainer as the as the async version (I2S).

LGTM3

Reply all
Reply to author
Forward
0 new messages