Re: [whatwg/streams] Do not allow abort to happen when a close is about to happen (#634)

This looks okay to my brief review, but I'd like to think a bit more about whether the behavioural changes make sense.

`write(); close(); abort()` behaving differently from `close(); abort();` is WIA. My view of the contraints is:
1. Underlying-sink write() and close() should be treated as atomic
2. abort() should happen ASAP but without violating 1.
3. Underlying-sink abort() should never be called after underlying-sink close(). ← New with this change

I am optimistic about the potential of leveraging the [[queue]] to get the right behaviour. That might be the simpler implementation I was grasping for but couldn't quite reach.

-- 
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/pull/634#issuecomment-270561679