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

@domenic Please take another look. As mentioned above, I had to add an exception for `string | async iterable<T>` overloads, so that string objects resolve as `string` rather than `async iterable<T>`.

This was discovered while we ran an experiement allowing `async iterable<T>` in `Request`/`Response` bodies.

I also realized I did not implement the union resolution previously (only the overload resolution). That is now fixed.

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

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