The motivation for destructuring is to tersely do algorithmic stuff using a
value from an object, e.g.
```
const {x, y} = coordinates
//Do a whole bunch of stuff using x here...
```
It seems to me, that destructuring into an object loses the whole purpose
of destructuring, e.g.:
```
const
Definitely agree with isiah and kai. The proposal original mentioned is not
as readable as its less-terse counterparts. I'm all for less code that does
more, but not at the expense of not being able to easily look at the code
and understand what's going on. And if not, there had better be a good
bject: Re: Picking (deconstructing) properties into object literals
-1 and agree with isiah
furthermore, i see javascript deconstruction as a never-ending can-of-worms
that too-often devolves into ruby-esque confusion / arguments over the “best”
way to do assignments. NO AMOUNT of lan
-1 and agree with isiah
furthermore, i see javascript deconstruction as a never-ending can-of-worms
that too-often devolves into ruby-esque confusion / arguments over the “best”
way to do assignments. NO AMOUNT of language-spec changes will resolve all
these arguments, so forget about it.
Honestly, I'm not sure how necessary this really is. `_.pick` exists
in Lodash, Underscore, and Ramda, but I'm not seeing it in persistent
data structure libraries like Immutable.js [1] or Mori [2], where it
would seemingly be *more* critical.
[1]:
5 matches
Mail list logo
