Tracking bug and discussion for asynchronous iteration in Node.js core

[vsemozhetbyt]

Asynchronous iteration has landed in V8 6.3 , so we can have it in Node.js v9 at the end of the year.

There are some plans to implement a stream version based on this feature. Since node-eps seems to be archived, maybe it is worth to have an issue for this in the core repository.

Refs:

https://github.com/tc39/proposal-async-iteration
https://tc39.github.io/proposal-async-iteration/
https://bugs.chromium.org/p/v8/issues/detail?id=5855

https://ponyfoo.com/articles/javascript-asynchronous-iteration-proposal
http://2ality.com/2016/10/asynchronous-iteration.html
https://jakearchibald.com/2017/async-iterators-and-generators/

nodejs/CTC#53
nodejs/readable-stream#254
tc39/proposal-async-iteration#74
nodejs/promises#31 (and nodejs/promises#31 (comment))

https://github.com/calvinmetcalf/async-iter-stream

[vsemozhetbyt]

Personally, I would look forward to a core way to read and process big files line by line in async/await functions without complicated Promise chains in event callbacks.

I understand this is not the main purpose of streams, but everybody loves fs or http anyway, so this is just a reminder to not forget readline.

[Fishrock123]

I'm not super familiar with async iterators but this seems like something we'd definitely want to investigate further.

[benjamingr]

AsyncIterator landed in Chrome and V9 will likely ship support. @nodejs/streams @nodejs/collaborators

I would love it if this issue made it to TSC agenda and discussed at the next meeting - I think adding experimental Symbol.asyncIterator support to streams behind a flag while explaining they don't perform as well as streams at the moment might be a good idea.

[calvinmetcalf]

I don't know if I'll have time for a pull request but if somebody wants to use the module I wrote as the basis for adding them to streams you have my permission to do so without worrying about the license.

[mcollina]

I don't think that placing them under a flag is helpful. I would just emit an experimental warning when using them for the first time.

[benjamingr]

@mcollina you're right, an experimental morning should be sufficient.

[mcollina]

I'm working on an implementation of this, and it is not clear when asyncIterator.throw(e)  is called.

[jasnell]

I've been playing with this a little bit in the fs promises implementation, specifically in a promise-based readFile() implementation and I have to say that using the async iterator works rather well. I'll be pushing the code up to a branch a bit later today.

[rektide]

Hey. I want to chip in for any Node.js users like myself, playing along at home, about how to use async generators in Node.js: that information was a little scattered, and I wasn't sure what the status was myself.

• Node versions 8.3 and above seem to have async iteration support! (Wow! That's way more support than I thought!)
• All versions of Node that do support async iteration require --harmony_async_iteration to get the feature. edit: Node v10 and up has async iteration on by default, Node v8.3+ requires --harmony_async_iteration.
• I tested with this sample script:

async function * answers(){
	yield Promise.resolve(42);
};
(async function universe(){
	for await (var answer of answers()){
		console.log(answer)
	}
})()

Thank you Node team and V8 implementer Caitlin Potter. This is such a great improvement to JavaScript.