Jesse Wright

As long as you are happy to include that kind of functionality in the main package I'm happy to split the files and add these extensions as separate files once...

Similar with the multiTransformIterator (should buffer the transformers but not their elements, ..., I think). The main downstream effects would be at https://github.com/comunica/asyncjoin/blob/main/join/DynamicNestedLoopJoin.js and https://github.com/comunica/asyncjoin/blob/main/join/NestedLoopJoin.js

I've added some more tests with the behavior I would expect [here](https://github.com/jeswr/AsyncIterator/tree/fix/empty-iterator-await) - but haven't yet had the time to find the root cause of the issue (and not sure...

So in doing working on https://github.com/RubenVerborgh/AsyncIterator/pull/36 I've discovered that this issue is not entirely resolved by changing the `autoStart` to be false by default since the `EmptyIterator` does not actually...

I'm thinking there are 2 solutions here - (1) Add a waitForEndListener similar to the `waitForDataListener` - (2) Inside `AsyncIterator` add the following methods, and call `_start` whenever `_sourceStarted` is...

That sounds like a good solution with expected outcomes @RubenVerborgh - I'll let you know if I have any more thoughts in modifying #36. This should only introduce a few...

@RubenVerborgh I made a start on it yesterday and will be try and do the rest today

Still working on this, I just wanted to check I'm on track with some of the decisions I have made in terms of other slight changes in behaviour as a...

TLDR; I agree with all the feedback; I have a lot more clarity on how to finish this off. > Are you introducing it for the case where an iterator...

@RubenVerborgh Apologies for dragging this out - another places that I just realised the original implementation was going against the `Readable` spec is the following: Calling readable.pause(), readable.unpipe(), or receiving...