unexpected CALL_START

[mgutz]

Unsure if this a real error or if I'm misusing object notation. Trying to avoid using {} around attributes in a template library.

# ok
t.a class:"btn", "<foo/>"

# unexpected CALL_START
t.a class:"btn", raw("<foo/>")

[TrevorBurnham]

Definitely a weird bug. Simplified test case:

a(b:c, d)    # works
a(b:c, f(d)) # fails

Putting explicit curly braces or parens around b:c fixes it. Pinging @michaelficarra... is this a dupe?

[mgutz]

same as #1615

[TrevorBurnham]

Ah, thanks for saving Michael the trouble!

[ali01]

Similarly, it looks like the following:

class Foo
   @bar = =>
     new @ aoe : 3

Foo.bar()

fails to parse (with Unexpected 'CALL_START'). Whereas the same code with parens around the object after new, succeeds:

class Foo
   @bar = =>
     new @(aoe : 3)

Foo.bar()

[vendethiel]

As said before #1111, #1615