-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial: Add subscripts to BindingIdentifier static semantics. #1885
Editorial: Add subscripts to BindingIdentifier static semantics. #1885
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I like listing these when they actually affect the semantics.
@marjakh would you mind registering as a contributor? https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md#required-legal-agreements |
I work at Google and I was under the impression we're covered somehow. Isn't that the case? This is my second contribution and I don't remember what i did the first time, whether I registered to something or not. It was a while back. I can try to search my e-mail for history, if needed. |
This is a good point, though unfortunately there's no easy way to check for employer. The best approximation we came up with is check for public membership in https://github.com/googlers. @marjakh Could you please join that at go/github, then go to https://github.com/googlers, search for your handle and set your membership to Public? |
Done! |
Yes, people who work for member companies are generally covered, and should not sign the contributor form. Glad this has been sorted out. |
Adding subscripts here makes sense, because the semantics specifically talk about the presence of a parameter. Also, the productions below, where the semantics also talk about the presence of a parameter, already have the subscripts. So it's inconsistent to not have them here.
Adding subscripts here makes sense, because the semantics specifically talk
about the presence of a parameter.
Also, the productions below, where the semantics also talk about the presence
of a parameter, already have the subscripts. So it's inconsistent to not have
them here.