Jesse Wright
Jesse Wright
For basic methods like `.map` and `.filter`, on `AsyncIterator`, using the `SimpleTransformIterator` introduces uneccessary overhead via the `readAndTransformSimple` operator. To improve performance in applications like Comunica it may be worth...
supercedes #65 The bolded performance regression needs to be ironed out first. Before For loop with 5x10^9 elems: 5.207s UnionIterator 2x10^7 iterators: 30.297s **UnionIterator 1000x500 iterators: 1.897s** UnionIterator 1000x500 iterators...
As discussed in https://github.com/RubenVerborgh/AsyncIterator/pull/75#issuecomment-1168219877. TODOs - Add more coverage - See if https://github.com/RubenVerborgh/AsyncIterator/blob/3a5b62cf8ca00e60013b6aa7c1e692b26fcb6964/asynciterator.ts#L905-L911 is necessary. @RubenVerborgh the question here is - can we just assume the `root` is `.readable` if...
Resolves #66 This PR introduces a `maybeIterator` which takes an iterator as input, and returns an iterator *only if* it is non-empty. Otherwise null is returned. Happy to accept naming...
This add the method .uniq the the AsyncIterator which captures a common pattern used with AsyncIterators of filtering elements in the iterator such that only unique elements are passed through....
resolves https://github.com/RubenVerborgh/AsyncIterator/issues/25 resolves https://github.com/RubenVerborgh/AsyncIterator/issues/35 Part of https://github.com/RubenVerborgh/AsyncIterator/pull/43 without any lint or limit changes
Apologies in advance that this issue is not very concrete! I'll elaborate more once I get a chance to do some proper profiling. After running [this benchmark](https://github.com/comunica/comunica-feature-reasoning/blob/chore/benchmark-forward-chaining/packages/actor-rdf-reason-forward-chaining/perf/ActorRdfReasonForwardChaining-perf.js) on the forward...
If I install the `asynciterator` package in a new node project, then methods like `.on` are not shown in my type hints because TypeScript cannot guess the type of `EventEmitter`...
I suspect that this may be caused by https://github.com/RubenVerborgh/AsyncIterator/issues/35 so don't worry for now. --- This is a potential issue that I saw when perf testing the current PRs, but...
In order to support some more niche use-cases I am coming across I was wondering if it is worth creating an `AsyncIterator-ext` package (see example below). IMO the best way...