Proposal to add keyword "nowait"
isiahmeadows at gmail.com
Mon Feb 12 05:59:31 UTC 2018
Yeah, and given it's the default, I'm not persuaded of the benefit to be
(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> wrote:
> This certainly doesn't sound backwards compatible. Also, this is something
> that type checking systems (like typescript and flow) are very good at
> On Feb 11, 2018 22:41, "Александр Ефремов" <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
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss