Lexer: Within inline if block, a throw that takes implicit object will split the object into multiple objects

[KarlPurk]

I apologise if this has already been reported, I did search the issues but there are lots related to "throw". Also, this may not be an issue, but I wanted to double check anyway.

When throwing exceptions the following syntax does not compile correctly:

if 1 then throw
    type: 'a'
    msg: 'b'

The above coffeescript compiles to the following:

if (1) {
  throw {
    type: 'a'
  };
}

({
  msg: 'b'
});

In order for this to compile we must use one of the following variations:

if 1 then throw type: 'a', msg: 'b'

or

if 1 then throw {
    type: 'a'
    msg: 'b'
}

or

if 1 
    throw
        type: 'a',
        msg: 'b'

Is this intended? Or are we missing out on a nicer syntax for throwing exceptions?

Thanks!

[GeoffreyBooth]

Duplicate of #1263. The issue is the object without braces as part of a statement. That would be nice to fix, if someone feels like submitting a PR; but the workaround is to just add braces, or define the object into a variable before throw or returning it.

[GeoffreyBooth]

Actually it’s not a duplicate of #1263. Possibly a duplicate of #4150.

[GeoffreyBooth]

One more try: maybe a duplicate of #2998.