Jacopo Scazzosi

> That is expected; but what we need to know is the behavior for repeated pushes and pulls, cfr. https://github.com/RubenVerborgh/AsyncIterator/issues/60#issuecomment-1088528533 As far as my understanding goes and limited to cloning,...

> But that's because no data is ever pulled from it. Yes, precisely! What I meant in https://github.com/RubenVerborgh/AsyncIterator/issues/44#issuecomment-1103902591 is that, given that `HistoryReader` only pushes to its internal buffer while...

Update for posterity and to keep track of the general progress on this. Tagging @rubensworks @jeswr @RubenVerborgh . Open PRs that we're working on, to be reviewed / merged /...

We're halfway through! Faster unions are next. @RubenVerborgh @jeswr @rubensworks do you think we can get these merged by the end of august?

@RubenVerborgh @jeswr perhaps it would make sense to do faster unions and the synchronous transform iterator first, wrapping up 3.x, and leave end on read last. Would that work for...

Update for posterity and to keep track of the general progress. Tagging @rubensworks @jeswr @RubenVerborgh . Open PRs that we're working on, to be reviewed / merged / rebased in...

Should this be a part of the changes summarized at https://github.com/RubenVerborgh/AsyncIterator/issues/44#issuecomment-1166907641 ?

> my laptop appears to have to deal with a large number of memory leaks when it shuts down Interesting. Does that imply that there's memory that isn't being returned...

I'm not entirely sure about my assumptions here but this should generate a significant amount of CPU contention between iterators as we're still single-threaded (-ish, I know there's some magic...

If we're talking about something for the next major release, I would also suggest getting rid of commodity prototypal methods entirely as they bind classes to one another, preventing tree-shaking.