4 ms·

Is this part of the standard?

• paulddraper 7y ago
  Did you read the commit? The spec material was linked: https://tc39.es/proposal-top-level-await/#sec-execute-async-module https://tc39.es/proposal-top-level-await/#sec-execute-async-... It's a Stage 3 proposal https://github.com/tc39/proposal-top-level-await https://github.com/tc39/proposal-top-level-await
  • lacampbell 7y ago
    I did. It looked like a diff, and since I don't have much interest in the internals of v8 I closed the tab. Welcome to the internet!
• mstade 7y ago
  It's a stage 3 proposal[1], which according to the TC39 process[2] means "the solution is complete and no further work is possible without implementation experience, significant usage and external feedback." In other words, it's all but standardized. Barring significant blockers coming from actual implementation experience this will most likely be ratified. [1]: https://github.com/tc39/proposal-top-level-await https://github.com/tc39/proposal-top-level-await [2]: https://tc39.es/process-document/ https://tc39.es/process-document/
  • Klathmon 7y ago
    And the way the TC39 works, it won't progress until multiple vendors can implement it. Being implemented by multiple js engines is how JS features become standardized.
    • mstade 7y ago
      Yup, thanks for adding that. It's a good process I think, though it is kind of a double edged sword. On the one hand it's nice because it means the standard isn't bloated with a bunch of stuff that no one implements, but on the other hand it also means it's much harder to get rid of stuff that turns out to maybe not be such a great idea after all, leading to bloat anyway. Still, it's a pretty good process I think.