Top level awaits about proposal-async-await

[domenic]

We specifically reserved await at top-level in modules to account for this possibility. Nobody's had the time to really figure out the semantics yet, though.

[ivan-kleshnin]

Oh, cool, thank's for the response.

[zenparsing]

We're probably not ready for this yet, but for the record there are two solutions that make sense to me:

For server-side systems, it makes sense to me to have a main function which defines program entry. If the executed module exports a main function, then it would run that. The main function could be an async function.

Also, if we ever get do-expressions, then it would makes sense to also have a do-async-expression.

do async {
  let x = await a.doStuff(); 
  let y = await a.doOtherStuff(x);
}

My personal opinion is that we should not allow modules themselves to be async, for simplicity and separation of concerns. Also, I don't think we want to outright reject the possibility of a system which loads modules synchronously and doesn't need to worry about async within the module system itself.

[lukehoban]

Note that there is also quite a bit of discussion on this same topic in #9.

I'll close this issue to keep a single thread of discussion on top level await.