Fix: modifying the name of a named function expression results in TypeError only in strict mode #36803
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… strict mode
Description
In the "Named function expression", the name of the function expression is read-only. However, the name of the function is modified inside the function body and does not cause an error in non-strict mode. However, it only causes TypeError in strict mode.
Therefore, the corrective this code needs to put a
"use strict";
statement before any other statements to be correct, as demonstrated here:In Google Chrome, the result is as follows: (other browsers are similar)
Motivation
Additional details
Related issues and pull requests