Why does TypeMemberList separate members by semicolon instead of comma?

Topics: Language Specification
Dec 29, 2013 at 5:38 AM
Edited Dec 29, 2013 at 5:38 AM
I thought at first this was because the use of AssignmentExpression in certain contexts would introduce ambiguity, but it turns out that AssignmentExpression doesn’t allow commas, so I’m not sure what the answer is.

Interested to learn the reasoning behind why the grammar uses semicolons instead of commas like normal JS object literals. Not important at all, just wondering.

Thanks,