With ES6 having a production rule Declaration and ES5 having
FunctionDeclaration, I'm curious why a variable declaration (as we
say), officially VariableStatement, has not been originally defined as
a declaration (back then).
Would you consider it to be a declaration today if we didn't need
Thank you everyone for your input and explanation, I really appreciate
it!
I just wanted to say that I understand that those notes are not
normative, however, I also think they are tremendously helpful for
understanding more complex parts of the spec. I think they can be a
gateway until one
On 2015-02-02 09:46, Brendan Eich wrote:
That was simply for consonance with the other productions reached directly
from the Statement nonterminal.
That is my actual question: Was there a specific reason to make it a
/Statement/ as opposed to something similar like /FunctionDeclaration/,
[Section
14.2.17](https://people.mozilla.org/~jorendorff/es6-draft.html#sec-arrow-function-definitions-runtime-semantics-evaluation)
says
Any reference to `arguments`, `super`, or `this` within an
*ArrowFunction* are resolved to their bindings in the lexically
enclosing function.
However,
On 2015-01-21 10:21, Brendan Eich wrote:
Good catch, probably best to file a bug at this point:
http://bugs.ecmascript.org/
Filed as https://bugs.ecmascript.org/show_bug.cgi?id=3587
Thanks!
___
es-discuss mailing list
es-discuss@mozilla.org
Hi all!
I need some clarification around completion records.
Let me start with examples in the spec (7.0) and explain how I
understand them (and what I don't understand):
```
12.1.6 Runtime Semantics: Evaluation
IdentifierReference: Identifier
Return ?ResolveBinding(StringValue of
ot return a completion record (i.e. some do
and some don't).
2. Algorithms *always* return a completion record, but it's not always
*explicitly* stated in the algorithm.
Felix
On 2016-09-23 03:32, Bergi wrote:
Felix Kling wrote:
I need some clarification around completion records.
You'l
7 matches
Mail list logo
