Re: [whatwg/streams] us.abort() is not called if us.write() fails (#620)

**My severity analysis:**

Naively written sources and sinks will tend to leak resources. Some number of hours will be lost to debugging these resource leaks. Garbage collection will mitigate this issue for some Javascript-authored streams, but not all. For example, a WebSocket will stay alive as long as it is open and a message handler exists, so GC would not clean them up.

**My usability analysis:**

If `finally()` existed, it would be unambiguous what to do here. On the other hand, `abort()` or `close()` being called when there wasn't a corresponding `abort()` or `close()` at the reader/writer level might be considered confusing.

**My proposal**:

Do nothing now. Discuss adding `finally()` to sources and sinks as a "v2" feature.

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