multiple assignment about luna HOT 7 OPEN

100% with you!

from luna.

I prefer also the explicit-expand version:

a, b = *[1, 2]

so this:

a, b = [1, 2] will throw an error since every time I'm scared about:

a, b = c where c is an array, but how know?

So a, b = *c give me a more sense that the code is 'right'

from luna.

haha yeah I dont like all the flexibility ruby gives you there, all this crazy shit you have to parse out in your mind, for such little gain, but I would like to consider it for multiple return values. however even that has limited use, returning meaningful structs is better design. Even in js-land like returning [x, y] for a point and accessing [1] has no meaning vs .y etc, so it's kinda tempting to forget about this as well and keep things simple

from luna.

Yep, I see what you mean and I agree!

from luna.

sorry I guess it would be x, y = somethingThatReturnsAPoint(), but meh haha, pretty minimal win over p = something... I'm pretty jaded when it comes to simplicity, if it doesn't give you a major win I dont consider it much of a win at all. Ruby has tons of subtle conveniences but overall when I look at Ruby I just see a mess because hell you can define an array in like 16 ways with those weird % delimiter combo things etc

from luna.

What about destructuring then ? [a, b] = somethingThatReturnsAList()

from luna.

@Nami-Doc same thing really, I dont love nor hate it, im pretty impartial, so it's probably not worth complicating implementations. A limited subset might be fine, we'll see! It may be interesting from a pattern matching perspective in the future, the assignment portion I find a little boring

from luna.