Re: [heycam/webidl] Extending async iterators to support streams (#800)

I put up a draft at #808 but I didn't get to the part where `asyncIterable.values(...args)` gets the args passed to the async iterator initialization algorithm.

Memo to self: our argument list conversion routines all go through the overload resolution algorithm. Currently this accepts operations and extended attributes, the latter to support [NamedConstructor]. We could extend this to support async iterable declarations as well, and that's probably the path of least resistance. Then, maybe manually construct an effective overload set, pass it in, and use the arguments that result?

If we want to disallow overloads of async iterator declarations, then we could extract only steps 15-16 of the overload resolution algorithm, since they are the only ones applicable when there's no overloads. Disallowing overloads is probably necessary anyway, because we require all arguments to be optional?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/800#issuecomment-535839216