- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 26 Jul 2018 15:49:43 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 26 July 2018 22:50:05 UTC
I'm working on adding some examples to the spec in my spare time; I have them about half-completed. The argument against `Promise.resolve().then()` is severalfold: - Object allocation - Swallows exceptions and converts them into rejected promises - Bad layering: promises are layered on top of microtasks, but right now you need to use the high-level feature (promises) to get at the lower-level underlying capability (microtasks). We should just expose the lower-level feature. Not aware of many other unavailable timings, personally... maybe the different task sources the browser uses for task-queuing? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/294#issuecomment-408258727
Received on Thursday, 26 July 2018 22:50:05 UTC