Wrong interpretation involving property indentation

[mcmire]

Not sure if this has been filed before, but I notice this doesn't compile correctly:

prop: ->
  foo
    .bar 'baz', ->
      bliz
        .blaz 'zing', ->
          somethingHere()
        .fooz()
  someMoreStuffHere()

This compiles to:

({
  prop: function() {
    return foo.bar('baz', function() {
      return bliz.blaz('zing', function() {
        return somethingHere();
      }).fooz();
    });
  }
});

someMoreStuffHere();

when it should compile to:

({
  prop: function() {
    foo.bar('baz', function() {
      return bliz.blaz('zing', function() {
        return somethingHere();
      }).fooz();
    });
    return someMoreStuffHere();
  }
});

However, this gets interpreted correctly (i.e., outdenting one level):

prop: ->
  foo
  .bar 'baz', ->
    bliz
      .blaz 'zing', ->
        somethingHere()
      .fooz()
  someMoreStuffHere()

[showell]

+1 that this is a compiler bug, albeit an obscure one.

Here is a slight simpler repro of the behavior:

prop: ->
  foo ->
    bliz ->
      x
     .yo
  thisGoesToTheWrongPlace()

({
  prop: function() {
    return foo(function() {
      return bliz(function() {
        return x;
      }).yo;
    });
  }
});

thisGoesToTheWrongPlace();

If you move the ".yo" line one character in either direction, you get a more sensible interpretation from the compiler.

Here is my rant on whitespace.

[hookdump]

@mcmire : There's an ongoing discussion about whether this is a bug, or incorrect usage of indentation: #1435

@showell : I see no bug there! Only 1 missing space in ".yo" indentation... which of course confuses the compiler.

[showell]

@hookdump I think it's a bug that the compiler tries to translate confusing code. The "yo" is in a place that makes no sense in the first place; the compiler should just punt on it with an error.

[hookdump]

@showell Oh, you're right; although I would say it's a different issue than the one reported by @mcmire:

• @mcmire's involves valid indentation that produces incorrect compiled code.
• Yours involves invalid indentation not being treated as an error (and also producing incorrect compiled code).

Anyway, both look like problems that need to be checked out.

[michaelficarra]

@hookdump: I believe the initial bug reported by @mcmire is indeed a duplicate of #1435, as you stated earlier. The bug @showell is pointing out, though, is a duplicate of #1275. Since they're both duplicates, I'm going to close this.

edit: clarification