Even though this CL looks good I don't think we want this behavior.
The intent was that if the formal parameters are NOT simple, they should
behave
like strict formal parameters. That means, no duplicates, no eval/arguments
and
no strict future keywords.
With the current CL the following is valid
function f(...arguments) {
return arguments;
}
I'm pretty sure that we will have trouble with this as is.
https://codereview.chromium.org/924403002/diff/1/test/cctest/test-parsing.cc
File test/cctest/test-parsing.cc (right):
https://codereview.chromium.org/924403002/diff/1/test/cctest/test-parsing.cc#newcode4945
test/cctest/test-parsing.cc:4945: "...arguments",
Wow, that is terrible. I think this is a spec bug. We should treat
StrictFormalParameters the same as FormalParameters in strict functions.
https://codereview.chromium.org/924403002/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
