LGTM1

Stage 4 TC39 proposal already implemented elsewhere. Thanks for getting it into Chromium.

/Daniel

On 2026-08-05 14:40, Chromestatus wrote:
*Contact emails*
[email protected], [email protected]

*Specification*
https://github.com/tc39/proposal-joint-iteration

*Summary*
A TC39 proposal to synchronise the advancement of multiple iterators, often called zip.

*Blink component*
Blink>JavaScript>Language <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3ELanguage%22>

*Web Feature ID*
tc39-joint-iteration <https://webstatus.dev/features/tc39-joint-iteration>

*Motivation*
/No information provided/

*Initial public proposal*
/No information provided/

*TAG review*
/No information provided/

*TAG review status*
Not applicable

*Goals for experimentation*
None

*Risks*


*Interoperability and Compatibility*
/No information provided/

/Gecko/: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=2003333)

/WebKit/: In development (https://bugs.webkit.org/show_bug.cgi?id=303246)

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

/No information provided/


*Debuggability*
/No information provided/

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

*Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
No


*Flag name on about://flags*
/No information provided/

*Finch feature name*
V8Flag_js_joint_iteration

*Rollout plan*
Will ship enabled for all users

*Requires code in //chrome?*
False

*Tracking bug*
https://issues.chromium.org/issues/465357675

*Estimated milestones*
Shipping on desktop     153
Shipping on Android     153
Shipping on WebView     153



*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).

/No information provided/

*Link to entry on the Chrome Platform Status*
https://chromestatus.com/feature/6249068542164992?gate=6511364124311552

This intent message was generated by Chrome Platform Status <https://chromestatus.com>.
--
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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a732f49.01e193cf.3bb5d7.0337.GAE%40google.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a732f49.01e193cf.3bb5d7.0337.GAE%40google.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3660cfdf-9203-4145-895a-b83b57b64567%40gmail.com.

Reply via email to