Proposal to add keyword "nowait"

Александр Ефремов mr.efrem at gmail.com
Mon Feb 12 07:16:03 UTC 2018


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 <tj.crowder at farsightsoftware.com> написал(а):
> 
> 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, Александр Ефремов <mr.efrem at gmail.com <mailto:mr.efrem at gmail.com>> wrote:
> Sorry, but I didn’t understand you sentence. And I have knowledge in the promises of course.
> 
>> 12 февр. 2018 г., в 9:59, Isiah Meadows <isiahmeadows at gmail.com <mailto:isiahmeadows at gmail.com>> написал(а):
>> 
>> 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 <p.jaszkow at gmail.com <mailto:p.jaszkow at gmail.com>> 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, "Александр Ефремов" <mr.efrem at gmail.com <mailto:mr.efrem at gmail.com>> 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
>> es-discuss at mozilla.org <mailto:es-discuss at mozilla.org>
>> https://mail.mozilla.org/listinfo/es-discuss <https://mail.mozilla.org/listinfo/es-discuss>
>> 
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org <mailto:es-discuss at mozilla.org>
>> https://mail.mozilla.org/listinfo/es-discuss <https://mail.mozilla.org/listinfo/es-discuss>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org <mailto:es-discuss at mozilla.org>
>> https://mail.mozilla.org/listinfo/es-discuss <https://mail.mozilla.org/listinfo/es-discuss>
> 
> 
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org <mailto:es-discuss at mozilla.org>
> https://mail.mozilla.org/listinfo/es-discuss <https://mail.mozilla.org/listinfo/es-discuss>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180212/462d1635/attachment.html>


More information about the es-discuss mailing list