Use syntactic parameter for AssignmentExpression

I have met at least one ES6 enthusiast who found AssignmentExpression difficult to understand while trying to learn more about arrow functions. Can we replace all uses of AssignmentExpression except one or two to say, Expression[nocomma]? Even better, if spec-wise backwards compatibility is not a

Re: Make class constructors work with [[Call]] too?

(2013/07/02 13:09), Domenic Denicola wrote:> > Given that all non-primitive built-ins behave this way, and that > including `if (!(this instanceof ConstructorName)) { return new > ConstructorName(...args); }` is a well-established best practice for > ES5 code: Are you sure? What libraries do that?

Re: HTML date format and Date.parse()

(13/04/28 22:36), Allen Wirfs-Brock wrote: > For such interchange purposes, I don't think is is necessary to relax > the date format rules. Note that ISO 8601 says that formatting > simplifications such as leaving out the T is permitted with mutual > agreement between the parties interchanging a da

Re: An example of the third basic rule of semicolon insertion

(13/01/20 15:07), heathmatlock wrote: > Substitute "chance" for "check" in the previous email. (I couldn't find your previous mail either in my es-discuss folder or the online archive, though I noticed that this mailing list drops more mails than a usual mailing list at W3C.) > On Sun, Jan 20, 20

spread operator (...) as a new token

Is "..." a new token that should be listed in Punctuator. I think it should and it seems like a little miss for which I am happy to file a bug, but I am not so sure as the proposal[1] doesn't include it. It seems that Firefox implements it as a token. Test cases: function x(. ..y) {} functio

Confusion about different [[Scope]] between Function Declaration and Function Expression

(Resending on behalf of 张立理 because his mail didn't go through.) According to [section 13 Function Definition](http://ecma-international.org/ecma-262/5.1/#sec-13) of ECMAScript-262 5.1, the **Function Declaration** production and the **Function Expression** production are nearly the same, except

Re: The result of (0).toExponential(1)

(12/03/10 17:33), DX Jin wrote: > Later, I saw the ES5 draft history[1], Step 15 in the previous version of > the "Sunnyvale"( 23 Feb 2009 ) and step 8.a in the "Sunnyvale"( 02 March > 2009 ) are the same intention. > Step 15 in the previous version of the "Sunnyvale" is only execute if this > num

Renaming [[GetOwnProperty]]

(Sending on behalf* of Franky ) Dear everyone who diligently worked on ECMAScript Edition5, I am often confused by the name of the internal method [[GetOwnProperty]](p). This name, if read literally, would indicate that this method gets a property, but in fact this method returns a property descr