Intent to Ship: Iterator Join

[Chromestatus]

Contact emails

ol...@google.com

Explainer

https://github.com/tc39/proposal-iterator-join

Specification

https://tc39.es/proposal-iterator-join

Summary

A TC39 proposal to add to JavaScript a means to concatenate the contents of an iterator into a string. The `join()` method of Iterator instances is similar to `Array.prototype.join()`: it returns a string that is the concatenation of all elements produced by the iterator, separated by commas or a specified separator string.

Blink component

Blink>JavaScript>Language

Web Feature ID

tc39-iterator-join

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=2047995)

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

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?

No

Flag name on about://flags

No information provided

Finch feature name

V8Flag_js_iterator_join

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/465715798

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/5095183554314240?gate=4700765030580224

This intent message was generated by Chrome Platform Status.

[Vladimir Levin]

LGTM1

[Rick Byers]

I assume there is good Test262 coverage? LGTM2 if so (but please add a test262 link to the chromestatus entry for the record)

Rick

--
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/cd7ac5b4-b051-4e34-a1a7-f59ca8ad3aaen%40chromium.org.

[Alex Russell]

LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Olivier Flückiger]

Thanks all,

It's covered by test262 and we are running them. Somehow wpt.fyi was missing the entry, I'll look into it as soon as I get to it.

*oli

LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.