syntax regression with compound assignment against implicit object in 1.2.0

[vincentcr]

a combination of:

• obj ?= # object declaration
• and: foo = # other object declaration

makes the first declaration only take the first member.

Example:

create = ->
    obj ?=
        x: 1
        y: 2
    obj

foo = 
    bar: ->

console.log 'created:', create()

this outputs:

created: { x: 1 }

javascript (note the part with y:2):

(function() {
  var create, foo;

  create = function() {
    if (typeof obj === "undefined" || obj === null) {
      obj = {
        x: 1
      };
    }
    ({
      y: 2
    });
    return obj;
  };

  foo = {
    bar: function() {}
  };

  console.log('created:', create());

}).call(this);

[TrevorBurnham]

Confirmed. Under 1.1.3,

obj ?=
  x: 1
  y: 2

works as expected. Under 1.2.0 and current master, y: 2 is seen as a separate expression. Bisecting...

[TrevorBurnham]

The first bad commit is af0ee70, the special-casing that fixed #1903.

[jashkenas]

Fixed in the above commit -- our current unfinished behavior is a source of much trouble. It would be good to look into removing it entirely, and having the grammar be able to handle (and ignore) the indentation instead.