Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReadableStream async iteration #319

Closed
MattiasBuelens opened this issue Feb 19, 2024 · 1 comment
Closed

ReadableStream async iteration #319

MattiasBuelens opened this issue Feb 19, 2024 · 1 comment

Comments

@MattiasBuelens
Copy link

MattiasBuelens commented Feb 19, 2024

WebKittens

@annevk

Title of the spec

ReadableStream async iteration

URL to the spec

https://streams.spec.whatwg.org/#rs-asynciterator

URL to the spec's repository

https://github.com/whatwg/streams

Issue Tracker URL

No response

Explainer URL

whatwg/streams#1306

TAG Design Review URL

No response

Mozilla standards-positions issue URL

No response

WebKit Bugzilla URL

https://bugs.webkit.org/show_bug.cgi?id=194379

Radar URL

rdar://problem/96318671

Description

This change to the Streams standard adds support for the async iterable protocol to the ReadableStream API, enabling readable streams to be used as the source of for await...of loops.

Spec change landed in whatwg/streams#980 and whatwg/streams#1035. (Yes, this spec change is already four years old. We forgot to ask for an official position from WebKit back then, so the second best time is now. 😅)

WPT tests are in streams/readable-streams/async-iterator.any.js.

Firefox has shipped this in 2023 in version 110 (see caniuse), and Chrome is currently implementing this (see feature on ChromeStatus).

@annevk
Copy link
Contributor

annevk commented Mar 6, 2024

I suggest we mark this as "position: support" one week from now, barring any objections. This is pretty much expected behavior for an API like this at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants