Object literals nest unexpectedly

[jed]

I'd expect

a: b: c
1: 2: 3

to compile to

({
  a: {
    b: c
  },
  1: {
    2: 3
  }
});

but it compiles to

({
  a: {
    b: c,
    1: {
      2: 3
    }
  }
});

instead. Is there any reason for this?

Having an un-indented element beneath another would indicate that they'd be on the same level, not nested. Thoughts?

[wiemann]

+1

[TrevorBurnham]

This is intentional, because it means you can write

func
  option1: 'foo'
  option2: 'bar'

instead of

func {
    option1: 'foo'
    option2: 'bar'
  }

This supports the common idiom of functions taking a single hash as a last argument. (The same thing is done in Ruby, which is part of why its DSLs are so pretty.)

Edit: Hmm, ignore what I just said. I'd expect the same output as jed. It's really weird that

func
  a: b: c
  1: 2: 3

compiles to

func({
  a: {
    b: c,
    1: {
      2: 3
    }
  }
});

Maybe @michaelficarra can tell us if there's an existing issue on this...

[geraldalewis]

#1116 ( and #1564, #1550 ). It's in the as soon as a patch is available milestone.

[michaelficarra]

@geraldalewis: beat me to it. Closing as duplicate of #1116.

edit:

as soon as a patch is available

Eh, I'm not so sure the discussion has reached agreement. I'll remove it from the milestone.

[jed]

thank you, @geraldlewis and @michaelficarra, and sorry for the redundant issue (though it seems like it comes up enough that it might merit some attention).

[geraldalewis]

@jed totally agree!

[jashkenas]

@jed et al ... this is now fixed on master, as a side effect of fixing #1903. You now get the expected compilation in the original post.