Leon Arnott (2015-02-17T13:03:30.000Z)
That line of code looks like it came directly from a test I wrote for
kangax's ES6 compatibility table.
Let's look at the test in its entirety:

```
try { eval('for (var i = 0 in {}) {}'); } catch(e) { return true; }
```
The grammer you describe is correct: ES6 no longer supports this useless
form. So, a conforming implementation must throw an error when the eval()
string is evaluated. If it does so, the test returns `true`, signifiying
conforming support.

I hope that answers your question - and pardon my presumptions if this test
code wasn't what you were thinking of at all.

-Leon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150217/dd8515ce/attachment.html>
d at domenic.me (2015-02-21T00:52:34.566Z)
That line of code looks like it came directly from a test I wrote for
kangax's ES6 compatibility table.
Let's look at the test in its entirety:

```
try { eval('for (var i = 0 in {}) {}'); } catch(e) { return true; }
```
The grammer you describe is correct: ES6 no longer supports this useless
form. So, a conforming implementation must throw an error when the eval()
string is evaluated. If it does so, the test returns `true`, signifiying
conforming support.

I hope that answers your question - and pardon my presumptions if this test
code wasn't what you were thinking of at all.