If I might, if there's one thing that has never particularly shone in JS, that is consistency.
I see only two possibilities here: 1) it throws with non Promises 2) it "Promisify" anything that's not a Promise as if it was a `Promise.resolve(1)` ... but since there's too much magic in the second point, I'd rather stick with the first one. Just my quick thoughts Best Regards On Fri, Jul 17, 2015 at 6:33 PM, Kevin Smith <[email protected]> wrote: > I know the spec for this isn't finalized, but what is the current >> direction for the behaviour when await is used on a function that is not >> marked async and doesn't return a Promise? Should it run immediately or >> wait for the next turn of the event loop? >> > > More generally, the question is: what should await do for non-promises? > > await 1; > > Should it force a job to be queued? > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
