[parser] report invalid rest parameter errors in Arrow functions

test/cctest/test-parsing.cc

Index: test/cctest/test-parsing.cc
diff --git a/test/cctest/test-parsing.cc b/test/cctest/test-parsing.cc
index bc12153729c622cf8ad031f2ae486a679949368a..e0eca42865e941ecb7c6d06ed3d86d42bc0c5fb1 100644
--- a/test/cctest/test-parsing.cc
+++ b/test/cctest/test-parsing.cc
@@ -7976,9 +7976,24 @@ TEST(EscapedKeywords) {
 
 
 TEST(MiscSyntaxErrors) {

[adamk, 2016/02/01 23:15:59]

Not sure this test makes any sense, some grouping seems like a good idea. I
liked before when these were up with similar bits (also, much easier to review
if you don't delete patch sets).

[caitp (gmail), 2016/02/01 23:19:38]

I was just getting rid of ones that weren't quite doing what they were supposed
to be doing yet, sorry.

I'll put them back with the Arrow function syntax tests

+  // clang-format off
   const char* context_data[][2] = {
-      {"'use strict'", ""}, {"", ""}, {NULL, NULL}};
-  const char* error_data[] = {"for (();;) {}", NULL};
+    { "'use strict'", "" },
+    { "", "" },
+    { NULL, NULL }
+  };
+
+  const char* error_data[] = {
+    "for (();;) {}",
+
+      // crbug.com/582626
+    "{ NaN ,chA((evarA=new t ( l = !.0[((... co -a0([1]))=> greturnkf",
+
+    // Simplified case:
+    "(...rest - a) => b",

[adamk, 2016/02/01 23:15:59]

Please add a test for the multi-arg version too (to make sure the preparser also
throws the error in that case).

[caitp (gmail), 2016/02/01 23:19:37]

Acknowledged.

+    NULL
+  };
+  // clang-format on
 
   RunParserSyncTest(context_data, error_data, kError, NULL, 0, NULL, 0);
 }