1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: reformat for-await-of

Browse Source 
Instead of `for`-`await`-`of`, prefer `for await...of`.

PR-URL: https://github.com/nodejs/node/pull/28425
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
This commit is contained in:
cjihrig 2019-06-27 13:49:58 -04:00
parent d22fbbe942
commit 6045fbbb5e
No known key found for this signature in database
GPG Key ID: 7434390BDBE9B9C5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/api/readline.md
View File

@ -322,7 +322,7 @@ changes:
Create an `AsyncIterator` object that iterates through each line in the input
stream as a string. This method allows asynchronous iteration of
`readline.Interface` objects through `for`-`await`-`of` loops.
`readline.Interface` objects through `for await...of` loops.
Errors in the input stream are not forwarded.
@ -556,7 +556,7 @@ rl.on('line', (line) => {
A common use case for `readline` is to consume an input file one line at a
time. The easiest way to do so is leveraging the [`fs.ReadStream`][] API as
well as a `for`-`await`-`of` loop:
well as a `for await...of` loop:
```js
const fs = require('fs');
@ -597,7 +597,7 @@ rl.on('line', (line) => {
});
```
Currently, `for`-`await`-`of` loop can be a bit slower. If `async` / `await`
Currently, `for await...of` loop can be a bit slower. If `async` / `await`
flow and speed are both essential, a mixed approach can be applied:
```js