I just considered this proposal in a context of `node.js` environment. I write microservices which execute requests to database and other microservices. All such requests are asynchronous. Therefore I execute them in body of async function. And sometimes I forget to add `await` for such operations. I thought that possible to implement that only for `async await` and didn't know that it transpiling to promises queue. I right understand that general problem in that?
> 12 февр. 2018 г., в 11:16, Александр Ефремов <[email protected]> написал(а): > > Yes, I was mistaken. That is possible only to do via type checking systems. > it's not work of javascript of the interpreter. Thanks for explanations. > >> 12 февр. 2018 г., в 10:32, T.J. Crowder <[email protected] >> <mailto:[email protected]>> написал(а): >> >> Previous discussion: >> https://esdiscuss.org/topic/async-await-await-async-a-simpler-less-error-prone-async-syntax >> >> <https://esdiscuss.org/topic/async-await-await-async-a-simpler-less-error-prone-async-syntax> >> >> -- T.J. Crowder >> >> On Mon, Feb 12, 2018 at 6:29 AM, Александр Ефремов <[email protected] >> <mailto:[email protected]>> wrote: >> Sorry, but I didn’t understand you sentence. And I have knowledge in the >> promises of course. >> >>> 12 февр. 2018 г., в 9:59, Isiah Meadows <[email protected] >>> <mailto:[email protected]>> написал(а): >>> >>> Yeah, and given it's the default, I'm not persuaded of the benefit to be >>> gained here. >>> >>> (Most feature requests like these in my experience come from such users who >>> use `async`/`await` without learning promises first. Without that >>> knowledge, people typically don't get that it's merely syntax sugar for the >>> common case, and they rarely understand that `async`/`await` is not >>> obligatory to use async functions. When users realize that, this really >>> does begin to seem superfluous, since the absence of a keyword or >>> `.then`/`.catch` implies you're not awaiting.) >>> >>> >>> On Mon, Feb 12, 2018, 00:44 Peter Jaszkowiak <[email protected] >>> <mailto:[email protected]>> wrote: >>> This certainly doesn't sound backwards compatible. Also, this is something >>> that type checking systems (like typescript and flow) are very good at >>> catching. >>> >>> On Feb 11, 2018 22:41, "Александр Ефремов" <[email protected] >>> <mailto:[email protected]>> wrote: >>> Sometimes when create the async functions forget to add await and later >>> such mistake difficult to find. >>> Maybe would be better always demand to add keyword nowait to calls >>> returning promises which we don't plan to wait. But if this keyword and >>> await keyword no exists then throw the error. >>> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] <mailto:[email protected]> >>> https://mail.mozilla.org/listinfo/es-discuss >>> <https://mail.mozilla.org/listinfo/es-discuss> >>> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] <mailto:[email protected]> >>> https://mail.mozilla.org/listinfo/es-discuss >>> <https://mail.mozilla.org/listinfo/es-discuss> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] <mailto:[email protected]> >>> https://mail.mozilla.org/listinfo/es-discuss >>> <https://mail.mozilla.org/listinfo/es-discuss> >> >> >> _______________________________________________ >> es-discuss mailing list >> [email protected] <mailto:[email protected]> >> https://mail.mozilla.org/listinfo/es-discuss >> <https://mail.mozilla.org/listinfo/es-discuss> >> >> >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
