`async iterable` is now `async_iterable`

[AtkinsSJ]

What is the issue with the Streams Standard?

As of whatwg/webidl@d5cc64c, the IDL type is now async_iterable as one keyword, instead of async iterable. This affects ReadableStream in the current spec, and also the changes in #1310.

[annevk]

cc @saschanaz

[saschanaz]

I don't think I have the write permission to change it, although anyone can open a PR.

[saschanaz]

Eh, but we don't use async iterable as an IDL type in Streams, so I think this can be safely closed?

[MattiasBuelens]

Indeed. We currently only use an async iterable declaration, we don't (yet) use an async iterable type. So the current standard doesn't need any changes, only #1310 does.

Side note: shouldn't the heading of 2.13.29 say "Async iterable types — async_iterable<T>" (with an underscore) now? There are still quite a few occurrences of "async iterable<T>" (with a space) in the WebIDL spec text.

[AtkinsSJ]

Indeed. We currently only use an async iterable declaration, we don't (yet) use an async iterable type.

Oops. That's quite a confusing distinction. 😅

For context: I saw that spec change got merged, searched Ladybird's IDL files for "async iterable", and ReadableStream was the only result. My apologies if this is a false alarm!

[annevk]

It actually seems weird to me we left the declaration without underscore. Was that intended @saschanaz?

[saschanaz]

Yeah, because otherwise we'll get the same LL(1) problem