Ruben Taelman

@jeswr Do you think think the slowdown is caused by the complexity of the code in `readAndTransformSimple`, or the fact that it fills an internal buffer? If the latter, just...

In Comunica, we also always include types as actual dependencies. For things such as `@types/node`, we use the version `*` range, so that the dep will always be available, but...

@jeswr Great idea! Could you have a first go at writing out a bounty issue over at the Comunica repo? Depending on what you have in mind exactly, it might...

I suspect you're running into an autoStart issue (see some of the closed issues here). By default, asynciterators will start automatically after creation. That means that if the iterator is...

I'm fine with either option. @RubenVerborgh what option do you prefer?

> So what I think @rubensworks wants is not for streams to not buffer, but for empty streams to (oh irony) not auto end. Exactly. Buffering itself is no problem....

> @rubensworks Do you imagine this will cause many problems downstream in Comunica (I shouldn't think so since it didn't have access to .pause or .readableFlowing in the original version)?...

Related to this. If we invoke `transform` on an iterator with `autoStart` set to `false`, should this new iterator inherit `autoStart: false`? (This seems to be not the case at...

> what kind of problems are you envisioning? Not sure. I just remember spending a lot of time debugging things related to `autoStart` :-) But if everything related to `autoStart:...

Also wondering about time. I hope to enter beta testing for Comunica 2.x later this week.