-
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 description to Function Environment Records #3401
Conversation
This resolves an inconsistency in the paragraph (that goes back to ES6), but I wonder if it should have gone the other way (adding "function" to the first occurrence)... The phrase "the function is [not] an |ArrowFunction|" is technically a category error, since a function is an Object (a language value), whereas an |ArrowFunction| is a Parse Node (a spec value). Saying "an |ArrowFunction| function" avoids the category error, but isn't much clearer, because the spec doesn't define what "an |ArrowFunction| function" is. I imagine it's a function that was created by evaluating an |ArrowFunction| expression. But if we expect readers to fill in that gap, then maybe it's okay to expect them to make sense of the category-error version. |
@jmdyck You reminded me that function is an |
It's not even correct, there's also |
@michaelficarra Yeah, you're right. I can update it. :-) 15.3.4 Runtime Semantics: InstantiateArrowFunctionExpression 15.9.4 Runtime Semantics: InstantiateAsyncArrowFunctionExpression |
f57b25e
to
c720771
Compare
About this sentence: |
@michaelficarra And, |
If use |
c720771
to
6b48958
Compare
Already update it, @jmdyck @michaelficarra Can you review it? |
No description provided.