Re: [whatwg/streams] Cancelling and exception handling async iteration of ReadableStreams (Issue #1255) from Mattias Buelens on 2023-02-08 (public-webapps-github@w3.org from February 2023)

From: Mattias Buelens <notifications@github.com>
Date: Wed, 08 Feb 2023 04:13:17 -0800
To: whatwg/streams <streams@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/streams/issues/1255/1422499557@github.com>

@domenic What are your thoughts on this? Should it be possible to cancel the stream *immediately* through its async iterator, and have those pending reads become rejected? (Or I guess they should actually become resolved...)

Was there a reason why we needed all `next()` and `return()` calls to be queued for WebIDL's async iterator machinery? Is this something ECMAScript expects from the async iterator protocol?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1255#issuecomment-1422499557
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1255/1422499557@github.com>

Received on Wednesday, 8 February 2023 12:13:30 UTC