AsyncIterator

AsyncIterator copied to clipboard

Perf/fast unions

18

Supercedes #79 The concerns about behavior (and reasons for a major version bump) that I pointed out there still remain. But not sure if I have a good solution for...

jeswr

Discussion: Destroy propagation in callback-based TransformIterator

2

I don't think it's really a bug, but nevertheless, I think it deserves some discussion. Yesterday, I discover some edge-cases in which chained iterators would keep on running (due to...

rubensworks

RubenVerborgh

Fix: explicitly add ESM types

2

Stumbled upon some unexpected behavior when having AsyncIterator as a (sub)depenency of a TypeScript project with configured to use the `Node16`, `NodeNext` or `Bundler` module resolution mechanisms. This probably did...

termontwouter

Make iterators AsyncIterable, Closes #89

6

While this will likely come at the cost of lower performance compared to plain data-events, we should add this for use cases where code readability is preferred over performance.

rubensworks

`AsyncIterator` type is not covariant

1

I would have expected the `AsyncIterator` type to be covariant; that is, I would expect to be able to do something like: ```ts declare const oneIterator: AsyncIterator; const numberIterator: AsyncIterator...

Peeja

Per @rubensworks comment https://github.com/comunica/comunica/pull/1165#issuecomment-1459611072; it would be useful to have a debug mode for asynciterator. The most straightforward approach would look something like ```ts const iterators = []; process.on('exit', ()...

jeswr

Intermediate async iterator does not correctly emit readable event, unpredictably

2

I'm getting a behaviour that appears to be caused by a residual task scheduler ordering issue, related to #28. I have a number of unit tests that involve async iterators...

gsvarovsky

As in https://github.com/RubenVerborgh/AsyncIterator/issues/86#issuecomment-1313381369

RubenVerborgh

What happens to iterators after they error?

4

Should they be closed? Destroyed? Should there be a special stated for iterators that errored? Or is recovery possible?

RubenVerborgh