W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

Re: Cancellation architectural observations

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 2 Mar 2015 15:21:29 -0800
Message-ID: <CAAWBYDD1PB9NZOo30OSpcqh94Owe=VzUDXWxNJ4U-q0XFSW0HA@mail.gmail.com>
To: Kevin Smith <zenparsing@gmail.com>
Cc: Dean Tribble <tribble@e-dean.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
On Mon, Mar 2, 2015 at 3:18 PM, Kevin Smith <zenparsing@gmail.com> wrote:
> I'm afraid I don't quite understand.  How is one supposed to create a
> cancelable task with async functions, under your proposed architecture?

I'm not sure!  The mapping between promises and async functions isn't
intuitive to me yet, and I'm not sure how async functions will be able
to produce promise subclasses rather than plain promises.

~TJ
Received on Monday, 2 March 2015 23:22:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 March 2015 23:22:17 UTC