Intent to Ship: Array.fromAsync

[Rezvan Mahdavi Hezaveh]

Contact emails

s...@chromium.org, rez...@chromium.org

Explainer

https://github.com/tc39/proposal-array-from-async

Specification

https://tc39.es/proposal-array-from-async

Summary

Array.fromAsync is the async version of Array.from. It takes async iterables, iterates them, and collects the results into an array.

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=1746209) This is a TC39 Stage 3 proposal.

WebKit: Positive This is a TC39 Stage 3 proposal.

Web developers: Positive (https://twitter.com/erickwendel_/status/1555206623836127232) Seems positive, lots of likes on Twitter.

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

It is debugged as any other static method in JavaScript.

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

Yes

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

Yes

https://github.com/tc39/test262/issues/3725

Flag name on chrome://flags

--harmony_array_from_async

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/v8/issues/detail?id=13321

Estimated milestones

DevTrial on desktop

120

DevTrial on Android

120

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/5069575759069184

This intent message was generated by Chrome Platform Status.

[Mike Taylor]

LGTM1. It's encouraging that Firefox Nightly shipped this a few months back with no reported regressions thus far.

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACJ3t%2Bg4MwKGhiGJg%2B0WdgJXTD0rGJ22ZFGAF8bnOtGoLhszzA%40mail.gmail.com.

[Mike Taylor]

Oops... sent too early. Can you also please request reviews for the rest of the review gates in the chromestatus entry?

[Shu-yu Guo]

Those gates are not applicable for most TC39 stage 3 features, including this one. Are you asking them to be marked as such or that we requested reviews for it?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/591771b3-56e8-4f56-aba2-f66241221d29%40chromium.org.

[Mike Taylor]

Sorry, we're still learning this new chromestatus process (and a similar concern came up in our API OWNERs meeting earlier today). My understanding is that we should have _something_ in there, so perhaps the right thing to do is to request the reviews stating that these are normally N/A for TC39 stage 3 features since we don't have a way for feature owners to mark something as N/A.

Johnny, does that sound right to you?

[Yoav Weiss]

LGTM2 % administrative shenanigans regarding the review gates

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c5219109-91f4-4816-a1b1-bc9d1a08236e%40chromium.org.

[Chris Harrelson]

On Wed, Oct 25, 2023 at 5:05 PM Shu-yu Guo <s...@chromium.org> wrote:

Those gates are not applicable for most TC39 stage 3 features, including this one. Are you asking them to be marked as such or that we requested reviews for it?

I think they are. TC39 stage 3 features can skip a TAG review and signals, but the other fields are still required.

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e_2hjvbBo5Bhpy7PfzxvEMH90ZnK%2B5_i8YQ2PoKFaS_bw%40mail.gmail.com.

[Johnny Stenback]

+1 to what Chris said. And if you feel a gate doesn't apply, you can state in a comment that you believe the result of the review should be n/a. And we're in fact in the midst of landing a short-hand button that does that for all approval gate chips.

Cheers,

Johnny

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_Hks-fS9hv%3D0q83FqzxDpp3MS5DpGicQiBrZwmzOK_%3DA%40mail.gmail.com.

[Chris Harrelson]

LGTM3

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACZRgz5HA6%3DygCeHUxTymz%3Dh4%2BgYc4-PGm0YTSg1EKC5Y8gGaA%40mail.gmail.com.