Report unexpected lexical decl also without destructuring

test/message/let-lexical-declaration-destructuring-in-single-statement.js

Index: test/message/let-lexical-declaration-destructuring-in-single-statement.js
diff --git a/test/message/let-lexical-declaration-in-single-statement.js b/test/message/let-lexical-declaration-destructuring-in-single-statement.js
similarity index 86%
copy from test/message/let-lexical-declaration-in-single-statement.js
copy to test/message/let-lexical-declaration-destructuring-in-single-statement.js
index dcfa6c14366c31175bc4043a74bfa49023389aaa..5e439fff9f203aac58591eb289de464d305f6d27 100644
--- a/test/message/let-lexical-declaration-in-single-statement.js
+++ b/test/message/let-lexical-declaration-destructuring-in-single-statement.js
@@ -2,4 +2,4 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-with ({}) let [a] = [];
+with ({}) let [a] = [42];

[vabr (Chromium), 2017/02/17 09:52:07]

Note: I added an element in the list on the right-hand side, to highlight that
the important error here is the lexical decl replacing a single statement, not
the failure to destructure an empty list.

[Dan Ehrenberg, 2017/02/17 09:54:35]

Note that that wouldn't fail anyway.

[vabr (Chromium), 2017/02/17 10:55:46]

Ah, interesting. I see now that 'a' will become undefined.
This is due to
"3. If iteratorRecord.[[Done]] is true, let value be undefined."
in [1]'s AssignmentElement block, right?

[1]
https://tc39.github.io/ecma262/#sec-runtime-semantics-iteratordestructuringas...