Closed MattiasBuelens closed 9 months ago
Apologies, I mean to file this bug on the (very similarly named) webidl2js project. 😅
Since the aforementioned spec change does not affect the Web IDL syntax, no action needs to be taken on the part of webidl2.js. Closing.
Haha that often confused myself too 😂
There's an edge case with the current Web IDL bindings for async iterators where manually calling
return(); next()
could result in thenext()
promise resolving before thereturn()
promise. The latest version of the Web IDL specification fixes this by updating the "ongoing promise" in the async iteratorreturn()
method.ReadableStream[@@asyncIterator]
)