- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 21 May 2019 18:34:55 +0000 (UTC)
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 May 2019 18:35:18 UTC
domenic commented on this pull request. > +being iterated over asynchronously to obtain a sequence of values. + +Note: In the ECMAScript language binding, an interface that is asynchronously iterable will have +<code class="idl">entries</code>, <code class="idl">keys</code>, <code class="idl">values</code>, +and {{@@asyncIterator}} properties on its [=interface prototype object=]. + +Prose accompanying an [=interface=] with an [=asynchronously iterable declaration=] must define a +<dfn id="dfn-get-the-next-iteration-result">get the next iteration result</dfn> algorithm. +This algorithm receives a <b>[=this=]</b> value, which is an instance of the [=interface=] that it +is defined for, and the <dfn export>current state</dfn>. +It must return a {{Promise}} that either resolves with undefined – to signal the end of the +iteration – or a tuple with three elements: + +1. a value of the first type given in the declaration; +1. a value of the second type given in the declaration; +1. an opaque value that is passed back to the next invocation of the algorithm, Let's stick with what you've got. Mixing yield/throw and promises is too weird, indeed. -- 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/pull/720#discussion_r286167523
Received on Tuesday, 21 May 2019 18:35:18 UTC