Andreas Kling 0255c8d976 Only apply auto-naming of function expressions based on syntax ... 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.		2021-03-22 12:44:07 +01:00
..
arrow-functions.js
constructor-basic.js
function-default-parameters.js
function-duplicate-parameters.js
function-hoisting.js	Libraries: Move to Userland/Libraries/	2021-01-12 12:17:46 +01:00
function-length.js
function-missing-arg.js
function-name.js	Only apply auto-naming of function expressions based on syntax	2021-03-22 12:44:07 +01:00
function-new-target.js	Libraries: Move to Userland/Libraries/	2021-01-12 12:17:46 +01:00
function-prototype-writable.js
function-rest-params.js
function-spread.js	Libraries: Move to Userland/Libraries/	2021-01-12 12:17:46 +01:00
function-strict-mode.js
function-this-in-arguments.js	Libraries: Move to Userland/Libraries/	2021-01-12 12:17:46 +01:00
function-TypeError.js