A big thing in a programming language for me is "glanceability" (ability to
glance at code and discern roughly what's going on).
Allowing destructuring braces to be mixed in object literals may well be a
natural extension of destructuring: I'm not denying that.
I just think that since they
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
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
> написал(а):
>
> Previous discussion:
>
Previous discussion:
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, Александр Ефремов
wrote:
> Sorry, but I didn’t understand you sentence. And I have knowledge in the
> promises
Sorry, but I didn’t understand you sentence. And I have knowledge in the
promises of course.
> 12 февр. 2018 г., в 9:59, Isiah Meadows написал(а):
>
> Yeah, and given it's the default, I'm not persuaded of the benefit to be
> gained here.
>
> (Most feature requests
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
Yes, agree that it doesn't backwards compatible. But type checking systems
(like typescript and flow) it's overhead for fast development.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
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, "Александр Ефремов" wrote:
> Sometimes when create the async functions forget to add await and
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
I had the same concern at first about confusing the destructuring braces with a
nested object literal. After looking at it some more it seems like a natural
extension of destructuring assignment.
___
es-discuss mailing list
es-discuss@mozilla.org
inline counter-rant.
> On Feb 8, 2018, at 9:04 PM, Bob Myers wrote:
>
> It does make one stop and wonder why the group will endlessly entertain
> trolls debating whether or not ES6 (or ES5) portends the end of civilization
> as we know it, while relentlessly ignoring literally
11 matches
Mail list logo