Should whitespaces be allowed in await.ops?

[JLHwung]

Among the . related grammar productions, both MetaProperty and MemberExpression allow whitespaces around .

new
////
  .target

We discussed in #10 that await* can be a thing, so we can look at YieldExpression: The YieldExpression allows whitespaces in yield * except line terminators between yield and *.

To align with current grammar and how JS developers feel about . notation. I think whitespaces should be allowed

awaitOps:
await . all
await . allSettled
await . race
await . any

I don't have strong opinion on line terminators. I am good with disallowing line terminators or allowing, and before . or/and after ..

[ljharb]

I’d personally prefer to forbid whitespace on either side of the dot, and i can’t recall the last time i even saw code that had any whitespace around the dot in any context - but consistency with new.target seems like the proper path to take.

[Jack-Works]

The current syntax doesn't allow space (or break lines) and I think we keep it.

[Jack-Works]

Oh I prefer to keep consistency with new.target and import.meta (if they accepts spaces)