Re: Re: Proposal to add keyword "nowait"

I think it should not be hard to implement at least for explicitely async functions. Of course it will miss non-async that return promises. But you can mark them as async. For example we are doing on each function that could return promise even if it doesn't use await. But even without it that

Re: async/await -> await/async: a simpler, less error-prone async syntax

I think there is something we could have right now to solve the problem of missing `await` without changes to the ES - it should be collored differently in IDE or texteditor you are using. Not like an error - because it's actually not. But to be obvious that "here" and "here" you have an `async`

Re: Thoughts on Partial Application

Hi There is already an issue on that https://github.com/rbuckton/proposal-partial-application/issues/13 2017-12-04 15:03 GMT+02:00 Michael Rosefield : > I was looking through the notes on the last meeting, in particular the bit > about Partial Application:

Re: Make comma at the end of line optional

Thank you for good summary. If this discussion would appears in future than your mail is a great link to starts from 2017-09-13 22:08 GMT+03:00 Jeremy Martin : > *> What am I missing?* > > Nothing with respect to function arguments, AFAICT. > > But to beat the

Re: Make comma at the end of line optional

Yes, this is the reason why I didn't mention the variable declaration in initial proposal - it is 100% valid syntax in current implementation (and 100% relative error in strict mode) But the design problems of ASI are incomparable with a special case of get and set 2017-09-13 17:55 GMT+03:00

Re: Re: Make comma at the end of line optional

Think of it from a different way: if there would be no ',' how would you react on the idea of adding it? Peaty sour every one would decide that would be a complete nonsense. On the other side there is a discussion about possibility of make it optional where different people have different

Re: Make comma at the end of line optional

> > You can try it yourself here: https://es6console.com/j7hy49k4/ > > > > On Tue, Sep 12, 2017 at 2:36 PM, Алексей <aga...@gmail.com> wrote: > >> Am... no. Right now this example would just not work. For now this code >> is invalid. >> >> 2017-09-12 21:

Re: Make comma at the end of line optional

similar to ASI, > where developers have to remember a list of exceptions before they elide a > comma. > > Even in the absence of backwards compatibility concerns, you need to > provide a persuasive argument that the cost-benefit ratio justifies the > effort, and judging from initial feedback,

Re: Re: Make comma at the end of line optional

com>: > Of course not: > ```js > var arr = [ > 1, 2, 3 > 4 > ]; > ``` > > If JS was the kind of language where a line break definitively ended a > statement, that'd be a different story - but it's not. > > On Tue, Sep 12, 2017 at 9:57 AM, Алексей <

Re: Make comma at the end of line optional

that gaps or their kind. 2017-09-12 20:32 GMT+03:00 Claude Pache <claude.pa...@gmail.com>: > > > Le 12 sept. 2017 à 18:57, Алексей <aga...@gmail.com> a écrit : > > > > Don't you think that line break is a strong punctuation by itself? > > I

Re: Re: Make comma at the end of line optional

Don't you think that line break is a strong punctuation by itself? 2017-09-12 19:54 GMT+03:00 Jordan Harband : > Punctuation isn't noise. > > On Tue, Sep 12, 2017 at 9:51 AM, dante federici < > c.dante.feder...@gmail.com> wrote: > >> I think the only place I see as a current

Re: Make comma at the end of line optional

Yes you are right it is not related to ASI in the implementation details. Only in form of usage 2017-09-12 19:40 GMT+03:00 Naveen Chawla <naveen.c...@gmail.com>: > I don't think ASI matters in relation to this proposal > > On Tue, 12 Sep 2017 at 22:05 Алексей <aga...@gmail.co

Re: Make comma at the end of line optional

// continuation of a previous line > } > > The `get` declaration actually *is* a valid declaration (see shorthand > property names here: https://developer.mozilla.org/en-US/docs/Web/ > JavaScript/Reference/Operators/Object_initializer# > New_notations_in_ECMAScript_2015). > > >

Re: Re: Make comma at the end of line optional

Will reduce the noise created around the real essence of a program 2017-09-12 19:27 GMT+03:00 dante federici : > What benefit does this give the language? > > ___ > es-discuss mailing list > es-discuss@mozilla.org >

Re: Make comma at the end of line optional

Sorry, but I don't see any problems with example you provide: const object = { get // not a complete declaration statement - so no implicit comma here y: 2 // continuation of a previous line z: x // complete declaration statement and next line is not an operator - implicit comma here in:

Make comma at the end of line optional

Hi all Now we have a great syntax improvement that allows us to put comma at the end of arguments lists, object and array definitions. So in multiline definition last line could have the same signature as others (not only in multiline, but multiline definition benefits the most). I would like to

Re: Math.sincos(x)?

If you think that performance of cos is too big (did you measure it?) than just calculate cos from sin with the formula sin^2 + con^2 = 1 ```js function sincos (a) { const sin = Math.sin(a) const cos = (1 - sin**2)**0.5 return {sin, cos} } ``` 2017-06-22 21:02 GMT+03:00 Robert Poor