You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we added TypeWithExtendedAttributes, we split up the DictionaryMember production into two cases:
required TypeWithExtendedAttributes identifier Default ;
Type identifier Default ;
We should remove the "Default" from the "required" case, since there is already prose that says:
A required dictionary member must not have a default value.
It's just that back when we had a single grammar production for dictionary members, with an optional "required" keyword at the front and "Default" at the end, this was not forbidden on the grammar level. But now it would be simple to forbid it there.
The text was updated successfully, but these errors were encountered:
When we added TypeWithExtendedAttributes, we split up the DictionaryMember production into two cases:
We should remove the "Default" from the "required" case, since there is already prose that says:
It's just that back when we had a single grammar production for dictionary members, with an optional "required" keyword at the front and "Default" at the end, this was not forbidden on the grammar level. But now it would be simple to forbid it there.
The text was updated successfully, but these errors were encountered: