[w3ctag/spec-reviews] Writable Streams (#163)

Hello TAG!

I'm requesting a TAG review of:

  - Name: Writable Streams
  - Specification URL: https://streams.spec.whatwg.org/#ws
  - Explainer, Requirements Doc, or Example code:
     - The specification section linked contains lots of examples of using writable streams
     - This section contains a high-level overview: https://streams.spec.whatwg.org/#ws-model
     - This section and others following it contain examples of creating writable streams: https://streams.spec.whatwg.org/#example-ws-no-backpressure
    - The FAQ contains some content on writable streams, although most of the frequently asked questions are about readable streams: https://github.com/whatwg/streams/blob/master/FAQ.md
    - The requirements document informed initial design work: https://github.com/whatwg/streams/blob/master/Requirements.md#creating-writable-streams
  - Primary contacts: @domenic, @ricea, @tyoshino

Further details (optional):

  - Relevant time constraints or deadlines: We are hoping to launch in Blink in M59, for which the branch point is in a couple weeks
  - [ ] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/): not applicable to this specification, as it specifies base primitives; future specifications which build on writable streams will likely make use of this, however.
  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)

You should also know that...

As this specification is for a base primitive applicable across all platforms, it does not use Web IDL, but instead is written in the style of the JavaScript specification.

We'd prefer the TAG provide feedback as (please select one):

  - [x] open issues in our Github repo for each point of feedback
  - [ ] open a single issue in our Github repo for the entire review
  - [ ] leave review feedback as a comment in this issue and @-notify [github usernames]

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/163