Commit 701392c

authored

Merge pull request #2413 from raycon/master

Change source of the term 'microtask'

2 parents 13da056 + 83b051e commit 701392cCopy full SHA for 701392c

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
@@ -23,7 +23,7 @@ Why did the `.then` trigger afterwards? What's going on?
`23`	`23`
`24`	`24`	`## Microtasks queue`
`25`	`25`
`26`		-Asynchronous tasks need proper management. For that, the ECMA standard specifies an internal queue `PromiseJobs`, more often referred to as the "microtask queue" (ES8 term).
	`26`	+Asynchronous tasks need proper management. For that, the ECMA standard specifies an internal queue `PromiseJobs`, more often referred to as the "microtask queue" (V8 term).
`27`	`27`
`28`	`28`	`As stated in the [specification](https://tc39.github.io/ecma262/#sec-jobs-and-job-queues):`
`29`	`29`
@@ -103,7 +103,7 @@ In the example above, `.catch` added by `setTimeout` also triggers. But it does
`103`	`103`
`104`	`104`	`## Summary`
`105`	`105`
`106`		`-Promise handling is always asynchronous, as all promise actions pass through the internal "promise jobs" queue, also called "microtask queue" (ES8 term).`
	`106`	`+Promise handling is always asynchronous, as all promise actions pass through the internal "promise jobs" queue, also called "microtask queue" (V8 term).`
`107`	`107`
`108`	`108`	So `.then/catch/finally` handlers are always called after the current code is finished.
`109`	`109`

Comments

(0)