Brian Kim

> Actually, now that I think about this “no differences between async generators and channels” rule it does not make much sense in a sense of extending possibilities of async...

> Async generators do not have utilities for manipulating them ex.: filtering, mapping, combining/merging, etc. I believe filtering/mapping can be easily done but more complicated scenarios of merging are much...

Reopening this cuz I plan on moving the combinator static method to a separate module and adding combinators.

Sorry for the sluggish response! I hear what you’re saying! I also sometimes wonder about writing simultaneously thenable/async iterable APIs. However, I’m not really sure baking this pattern into the...

Hahahaha if you make the observable.subscribe call a one-liner (maybe shorten `subscription` to `sub`), I will merge this in. Could be nice to show the flexibility of repeaters, how you...

Hmmm. So first things first: your use-case is probably best served by an async generator and not a repeater: ```js async function *gen() { await checkSomethingAsynchronously(); yield *someOtherRepeater; } ```...

I think I checked and found that `yield *` propagates return into the inner iterator immediately.

Hi just to be clear, is the issue jsdom doesn’t implement the EventTarget constructor and I should look elsewhere? Was trying to figure out why custom EventTarget.dispatchEvent stuff just failed...

I’m personally for having the poll interval reset on refetch! cc @benjamn @hwillson

Following up on the discussion today, I was wondering if we could also consider nullability syntax for input types? Like I said, I see the primary benefit of this proposal...