<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [ES6] Class method should not declare any variables to upper scope."
href="https://bugs.webkit.org/show_bug.cgi?id=150115#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [ES6] Class method should not declare any variables to upper scope."
href="https://bugs.webkit.org/show_bug.cgi?id=150115">bug 150115</a>
from <span class="vcard"><a class="email" href="mailto:utatane.tea@gmail.com" title="Yusuke Suzuki <utatane.tea@gmail.com>"> <span class="fn">Yusuke Suzuki</span></a>
</span></b>
<pre>Copied from <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [ES6] Class expression should have lexical environment that has itself as an imutable binding"
href="show_bug.cgi?id=150089">https://bugs.webkit.org/show_bug.cgi?id=150089</a>
Current Class expression implementation declares method names as a variable.
For example,
class A {
method() {
}
}
In the above case, we declare a variable `method` in the current implementation.
I guess this is the old draft behavior because I can't see any step in the current spec.
<a href="http://www.ecma-international.org/ecma-262/6.0/#sec-runtime-semantics-definemethod">http://www.ecma-international.org/ecma-262/6.0/#sec-runtime-semantics-definemethod</a>
As a result, if we evaluate the following,
class A {
1() {
}
}
We attempt to declare the variable `1`. We now wrap the class body with the class lexical scope. However, the lexical scope does not allow us to declare incorrect Identifier variable (like `1`). So assertion is fired.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>