Re: [streams] readable-stream-cancel.js "ReadableStream canceling an infinite stream" is flaky (#286)

Yes, please feel free to pull request.

In general I would like to reduce the use of setTimeout throughout the suite. The only potentially-legit cases I can think for it are where something should "never" happen (e.g. a promise should never be settled), we could use setTimeout(, 50) or so to check that. Otherwise we should in general save promises more and wait on them (pretty much every setTimeout(, 0) could be replaced by this).

Also: you may be interested in something I recently put together (https://github.com/whatwg/streams/commit/28f9bda6b2a4c4456b939b64f7ad32bdf128c015) that makes the tests runnable against your current browser: https://streams.spec.whatwg.org/tests/ Right now it is kind of tuned for Chrome (e.g. it lets `let`/`const`/iterators/`for-of` pass through instead of transpiling them) but I can tweak that if you can let me know what is supported by the browser you're developing on.

Finally if you're actively implementing you may want to weigh in on #253 where we're having an unfortunately-last-minute-feeling discussion that might end up changing the semantics of read()/ready/state to become an async read() :-S.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/286#issuecomment-74900321