mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-05-01 00:38:48 +00:00
The auto naming of function expressions is a purely syntactic decision, so shouldn't be decided based on the dynamic type of an assignment. This moves the decision making into the parser. One icky hack is that we add a field to FunctionExpression to indicate whether we can autoname. The real solution is to actually generate a CompoundExpression node so that the parser can make the correct decision, however this would have a potentially significant run time cost. This does not correct the behaviour for class expressions. Patch from Anonymous. |
||
---|---|---|
.. | ||
arrow-functions.js | ||
constructor-basic.js | ||
function-default-parameters.js | ||
function-duplicate-parameters.js | ||
function-hoisting.js | ||
function-length.js | ||
function-missing-arg.js | ||
function-name.js | ||
function-new-target.js | ||
function-prototype-writable.js | ||
function-rest-params.js | ||
function-spread.js | ||
function-strict-mode.js | ||
function-this-in-arguments.js | ||
function-TypeError.js |