Address further editor feedback

[rbuckton]

@bakkot: this is intended to address your feedback from #22 (comment) and #30 (comment).

I'm still considering if there's something more I need to do to address (await) => {} in a static block to reserve await for possible future support.

I've also taken the opportunity to update the baseline spec text that has changed since this spec was written (i.e., the introduction of ClassElementKind).

[bakkot]

LGTM

I'm still considering if there's something more I need to do to address (await) => {} in a static block to reserve await for possible future support.

For that point, I think it's probably OK to decide that (await) => {} is not legal in static blocks. I think you do need to call it out explicitly, somehow, since it's not totally clear whether the await in (await) => {} counts as "crossing function boundaries". I'm not sure exactly how to word that.

(FWIW I think the alternative you proposed, of parsing with [+Await] and forbidding AwaitExpression and for await, is probably simpler, but either approach should work in principle.)

[rbuckton]

I'll need to give more thought to the (await) case. There's also function await() to consider. It would be so much easier if await was just a ReservedWord in strict mode.

[JLHwung]

FYI Babel will disallow the following cases (babel/babel#12661):

class C { static { function await() {} } }
class C { static { (await) => {} } }
class C { static { ({ [await]: x}) => {} } }

This is to align with the fact that

class C { static = function arguments() {} }
class C { static = (arguments) => {} }
class C { static = ({ [arguments]: x}) => {} }

is forbidden.