ladybird/Userland
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
..
Applications Spreadsheet: Add an export wizard, and support for custom CSV exports 2021-03-22 07:43:58 +01:00
Demos LibGfx: Rename 32-bit BitmapFormats to BGRA8888 and BGRx888x 2021-03-16 11:50:03 +01:00
DevTools UserspaceEmulator: Add support for SC_abort syscall 2021-03-22 07:43:44 +01:00
DynamicLoader LibC: Add x86_64 Registers 2021-03-21 09:35:23 +01:00
Games LibGfx: Rename 32-bit BitmapFormats to BGRA8888 and BGRx888x 2021-03-16 11:50:03 +01:00
Libraries Only apply auto-naming of function expressions based on syntax 2021-03-22 12:44:07 +01:00
MenuApplets MenuApplets: Remove unused .gitignore files 2021-03-21 15:11:48 +01:00
Services Userland: Fix printf specifiers with off_t 2021-03-17 23:22:42 +01:00
Shell Everywhere: Remove pessimizing and redundant move() 2021-03-17 16:30:15 +01:00
Tests Tests: Create stress-writeread 2021-03-17 23:22:42 +01:00
Utilities profile: Add -a option as an alias for "-p -1" (all processes) 2021-03-21 16:02:11 +01:00
CMakeLists.txt Build: Build Userland with -O2, Kernel with -Os 2021-02-24 11:38:52 +01:00