- From: Daniel Ehrenberg <notifications@github.com>
- Date: Sun, 19 May 2019 15:15:39 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 19 May 2019 22:16:01 UTC
The [top-level await proposal](https://github.com/tc39/proposal-top-level-await) would make module evaluation result in a Promise, rather than synchronous success or failure. This would affect the [Update](https://w3c.github.io/ServiceWorker/#update-algorithm) algorithm, which takes the steps in 16.1 if there is such a failure. Does anyone have such concerns about this evaluation being asynchronous? If this seems alright, then I'll make sure we have a PR for ServiceWorker after top-level await reaches Stage 3. It looks like there would be a little bit of refactoring on the SW side, so I'll wait for things to settle down editorially on the TC39 side before making more churn with dependent specs. cc @domenic @guybedford @mylesborins -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1407
Received on Sunday, 19 May 2019 22:16:01 UTC