Benjamin Gruenbaum

@nodejs/test_runner @MoLow wdyt? FWIW: > Introduce a file-based customization of the test runner, including which tests to run, so that I don't have to pass the test filenames as arguments...

This isn't a "good first issue", I don't think "streams" and "good first issue" really mix except for tests/docs

> It just for await things for next tick (or anything else in next event loop). Note that `nextTick` is _opposite_ of "in the next tick". It's "in the current...

@jasnell technically #1 and #2 have different timings as well since they don't run on the same queue which is exactly the sort of implementation detail users shouldn't care about.

I'd love it if @domenic weighed in here too since (I think) he knows the most about `HostPromiseRejectionTracker`. I would love to help with anything Node related or with general...

@domenic so you're saying this should be tested in Node and web-platform-tests? That makes sense. Is there a formal (or not formal) process in the web-platform tests for ECMAScript removing/adding...

For analogy, C# does something like: ``` function flatten (this array) { return array.reduce( (a,b) => a.concat(b) ) } ``` Disadvantages are mostly the fact that any existing code cannot...

I'm not even sure what `combineLatest` would mean in a pull-based model, would you expect it to attempt to pull from all observables when it is being pulled from?

> Let's assume a very typical reactive programming use case, say, I need to combine a few streams into a single one, yielding value each time any of original streams...

Reminds me of https://github.com/tc39/ecmascript-asyncawait/issues/51 when I pondered if finally in await should even be allowed.