You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen a number of people confused that StrictFormalParameters does not imply strict mode code. I have definitely seen bugs introduced due to this confusion too, especially around non-simple parameter lists with opt-in behavior.
I've seen a number of people confused that StrictFormalParameters does not imply strict mode code. I have definitely seen bugs introduced due to this confusion too, especially around non-simple parameter lists with opt-in behavior.
A while back on #jslang we spoke about perhaps renaming StrictFormalParameters to something more reflective of the nature of preventing duplicates. I would instead propose that we add a note to 14.1.1 (https://tc39.github.io/ecma262/#sec-directive-prologues-and-the-use-strict-directive) or 14.1.2 (https://tc39.github.io/ecma262/#sec-function-definitions-static-semantics-early-errors) that a StrictFormalParameters production in a non-strict context does not imply strict mode code rules.
The text was updated successfully, but these errors were encountered: