Re: [whatwg/streams] Permitting transferable stream optimisation (#1124)

I wonder if we're overthinking this.....

There is an entity that has to "move along with the ReadableStream" to preserve sanity - containing at least the queue of outstanding items.
Do we have to make that object (and, if I understand correctly, the promises that the pullAlgorithm creates) Javascript observable in any realm?

If they are not observable, we can let the algorithm specify that these things must have the same effect as if it was implemented with promises in some realm, and cover the "optimizations" by the generic language that says "whatever implementation that produces the same observable effect as this algorithm is correct".

We may be clawing back observability that previously existed, which is a compatibility issue.


-- 
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/1124#issuecomment-955788983