News for hackers. Stuff that matters.
Re:Async Iterators: These Promises Are Killing My Performance by hetman on Sunday August 27, 2017 @11:17PM (#15114211)
I think the problem with yielding an array of lines is that all the code that uses the result of the function would have to be aware of this grouping of results all the way up the stack.

What he was proposing was a solution that looked like you were only returning one value per iteration (so none of the code doing the processing had to be aware there are arrays of values) but underneath the covers was actually being processed in batches on each run through the event loop.

It's actually a very elegant solution. The only code that would have to be aware that it's actually dealing with batches of values is the code producing those batches right at the top of the stack of calls.

Re:Async Iterators: These Promises Are Killing My Performance by Arnavion on Monday August 28, 2017 @01:36PM (#15118453)
That's correct, and I understand the author's solution. My point was that changing the spec is not a hard requirement, since it can be accomplished in user code.
Re:Async Iterators: These Promises Are Killing My Performance by hetman on Monday August 28, 2017 @08:17PM (#15121213)
Then I suppose we don't need async iterators at all since this can all already be done with callbacks.