It would be postponed to a later job, i.e., turn of the event loop. -- Cheers, MarkM
On Jun 26, 2015 11:49 AM, "Francisco Tolmasky" <[email protected]> wrote: > Apologies, I’m aware the last example didn’t make sense. What I meant was > more along the lines of the following: > > setImmediateOrOtherNextRunLoopMethod(function() { console.log(6) }) > console.log(await { then: function(x) { x(5) } }) > > In other words, would the “then” fire on the same run loop (since it isnt > a fancy Promise), or still have the underlying await engine (step function) > make sure it takes place on the next iteration (and in this case thus > possibly make it show up after the 6 instead of beefore). > > > On Fri, Jun 26, 2015 at 11:40 AM, Francisco Tolmasky <[email protected]> > wrote: > >> Out of curiosity, in ES7, would the following code: >> >> console.log(await { then: function(x) { x(5) } }) >> console.log(6) >> >> Print out 5 then 6, or still 6 then 5? In other words, is the >> asynchronousness gauranteed by the await, or by the underlying Promise >> implementation? >> >> >> -- >> Francisco Tolmasky >> www.tolmasky.com >> [email protected] >> > > > > -- > Francisco Tolmasky > www.tolmasky.com > [email protected] > > _______________________________________________ > 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
