Unable to decorate generator functions about babylon

[machty]

I'd love to be able to experiment with this syntax for ember-concurrency.com

Ember.Object.extend({
    @restartableTask
    *doStuff() {
      // ..
    }
})

but I'm running into this same issue. While there are probably a handful of things that need to be settled about decorators, @wycats tells me the above syntax is uncontroversial; would it be possible to sneak in a fix just for the above (without having to wait for a brand new plugin)?

[hzoo]

This is handled by #587 and will be in the next beta release which should be 7.0.0-beta.15 (soon)

[silkentrance]

@loganfsmyth It seems that Parser#parseDecorator() will swallow up the asterisk and parse everything until after the method's name, or rather what it considers to be a call expression, i.e. @decorator * gen() seems to be parsed as a single expression here, which it is not.

And since Parser#parseDecorator() calls upon Parser#parseMaybeAssign() I am quite unsure how to proceed further as this is being used all over the place.

Perhaps a little help from you guys?

[silkentrance]

For reference: @jayphelps proposed a different production for decorators here:
wycats/javascript-decorators#23 (comment)

[loganfsmyth]

Yeah I have no idea what the expectation was. When I originally directed you here I thought that the spec had already been updated to cover this. If it hasn't, I'm not sure there is much we can do until there's an official spec decision.

[silkentrance]

@loganfsmyth well, you seem to be the go-to guy in all aspects, so I thought that maybe you can call upon someone to also have a look into this, so maybe with the help of @wycats this can then be sorted out, chiming in the guys who implemented babylon and fixing the issues as the spec gets updated...
while I continue to figure out how the code works... 😁