News for hackers. Stuff that matters.
Re:Node v8.0.0 Released by koolba on Tuesday May 30, 2017 @05:08PM (#14448561)
Curious why?

I get the usefulness for arrays and object declarations. Particular to have cleaner diffs. But why for function calls?

Re:Node v8.0.0 Released by t1amat on Tuesday May 30, 2017 @05:33PM (#14448725)
Prettifying long function signatures and calls. You can spread them across multiple lines with the same trailing comma syntax you might use with a multiline array or object literal.
Re:Node v8.0.0 Released by epidemian on Tuesday May 30, 2017 @06:52PM (#14449219)
> Particular to have cleaner diffs. But why for function calls?

Exactly the same reason :)

Re:Node v8.0.0 Released by koolba on Tuesday May 30, 2017 @07:23PM (#14449383)
I suppose but that's usually an indication that an object would be more apt. If you have enough parameters that it needs to be wrapped, they're probably hard to track too.
Re:Node v8.0.0 Released by piezoney on Tuesday May 30, 2017 @10:59PM (#14450147)
Well no, since you can use object destructuring.

const fn = ( { arg1 = '', arg2 = [], arg3 = true } = {} ) => { }

Re:Node v8.0.0 Released by scottmf on Wednesday May 31, 2017 @04:49AM (#14451145)
But isn't this already valid with trailing commas?
Re:Node v8.0.0 Released by yzmtf2008 on Tuesday May 30, 2017 @07:42PM (#14449465)
One small benefit is that it's now easier to generate code.
Re:Node v8.0.0 Released by hajile on Tuesday May 30, 2017 @07:14PM (#14449335)
I like it for `compose()` function calls. Changing the parameters and order is fairly common, so the trailing comma becomes convenient for moving and adding parameters.