- From: Matthew Gaudet <notifications@github.com>
- Date: Wed, 20 Oct 2021 13:03:45 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 October 2021 20:03:57 UTC
So I just want to clarify the state of the world here, so I'm sure. The original issue (https://github.com/whatwg/streams/issues/933) was that the internals of `pipeTo` were visible. However, as Dominic hints above: We use promise resolution throughout the spec; is the position generally that visibility of the internals is bad, or just pipeTo? The impression I get from the writing around `forAuthorCode` was that it was only *internal* resolutions that were of concern (hence I'm not sure if we need to worry about `startAlgorithm` etc). I got around to testing my simplified test case above in Chrome, and realized that we do in fact observe the `Object.prototype.then` change, so I had originally misunderstood the intended scope. Could we potentially just revert https://github.com/whatwg/streams/pull/1045? -- 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/1178#issuecomment-947994479
Received on Wednesday, 20 October 2021 20:03:57 UTC