There's an edge case with the current Web IDL bindings for async iterators where manually calling return(); next() could result in the next() promise resolving before the return() promise. The latest version of the Web IDL specification fixes this by updating the "ongoing promise" in the async iterator return() method.
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])