Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd clarification that StrictFormalParameters does not imply strict mode code #618
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
added a commit
to bterlson/ecma262
that referenced
this issue
Sep 12, 2016
bterlson
referenced this issue
Sep 12, 2016
Merged
Editorial: %s/StrictFormalParameters/UniqueFormalParameters/g #690
bterlson
closed this
in
#690
Sep 12, 2016
added a commit
that referenced
this issue
Sep 12, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tcare commentedJun 22, 2016
•
edited
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.