- From: Adam Rice <notifications@github.com>
- Date: Fri, 26 May 2023 04:47:20 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 May 2023 11:47:27 UTC
The lack of "soft" errors in WritableStream was an intentional design decision to avoid situations where one of a number of queued writes fails and leaves the output corrupted due to the missing chunk. In File System, writing a chunk with a missing field is clearly an authoring error and I think making it recoverable would just encourage authors to not fix their bugs. The case of an "incorrect buffer size" with WebTransport datagrams is a weird one caused by us ascribing semantics to buffer boundaries in byte streams which was not intended by the streams specification. It can easily be averted by always using buffers of size 65536, so I'm not too worried about our unfriendly behaviour of erroring the whole stream. I think the absence of a hard/soft error distinction makes the standard more predictable and easy-to-use, even if in some cases richer error signalling would be attractive. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/1280#issuecomment-1564269454 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/streams/issues/1280/1564269454@github.com>
Received on Friday, 26 May 2023 11:47:27 UTC