Re: [whatwg/webidl] Add `async iterable<T>` type to WebIDL (PR #1397)

That also seems reasonable, but the problem is that any API currently accepting a string would need to juggle a lot of complexity to safely adopt `async iterable<T>`.

Perhaps there's a third solution whereby `string | async iterable<T>` cases involving a String object are resolved by going down the `string` path? But if there's no string in the type union we'd treat a String object as an Object for the purposes of `async iterable<T>`.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/pull/1397#issuecomment-2310027415
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1397/c2310027415@github.com>