Add class to existing lexical scoping tests

Add class to existing lexical scoping tests

This patch strengthens testing of classes by verifying that the binding
that they export externally follows block scoping, as opposed to var-style
scoping. The tests are based on existing tests for let and const.

R=adamk
LOG=N
BUG=v8:3305
Committed: https://crrev.com/e261540b9ee3182451faac7fcaba280b987cef10
Cr-Commit-Position: refs/heads/master@{#30140}

[Dan Ehrenberg, 2015-08-12 01:47:07]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-08-12 01:47:20]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1286923002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1286923002/1

[commit-bot: I haz the power, 2015-08-12 02:13:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-08-12 02:13:31]

Dry run: This issue passed the CQ dry run.

[adamk, 2015-08-12 03:36:49]

Glad to see these tests tightened up, this stuff was clearly under-tested before
(since class has its own path in the parser).

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/es6/block-scop...
File test/mjsunit/es6/block-scoping.js (right):

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/es6/block-scop...
test/mjsunit/es6/block-scoping.js:282: //assertEquals(1,f.foo());
Why is this commented out?

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
File test/mjsunit/harmony/block-scoping-sloppy.js (right):

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
test/mjsunit/harmony/block-scoping-sloppy.js:31: "use strict";
I don't think this should be strict...

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
test/mjsunit/harmony/block-scoping-sloppy.js:282: //assertEquals(1,f.foo());
Another odd comment; is something broken?

[Dan Ehrenberg, 2015-08-12 17:47:13]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-08-12 17:47:21]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1286923002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1286923002/20001

[Dan Ehrenberg, 2015-08-12 17:48:32]

The CQ bit was unchecked by littledan@chromium.org

[Dan Ehrenberg, 2015-08-12 17:51:48]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-08-12 17:52:02]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1286923002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1286923002/40001

[Dan Ehrenberg, 2015-08-12 17:53:01]

Fixed the issues, thanks.

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/es6/block-scop...
File test/mjsunit/es6/block-scoping.js (right):

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/es6/block-scop...
test/mjsunit/es6/block-scoping.js:282: //assertEquals(1,f.foo());
On 2015/08/12 at 03:36:49, adamk wrote:
> Why is this commented out?

Oh, because I had a test bug that I forgot about before mailing, and I didn't
notice this when I went over it... fixed now.

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
File test/mjsunit/harmony/block-scoping-sloppy.js (right):

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
test/mjsunit/harmony/block-scoping-sloppy.js:31: "use strict";
On 2015/08/12 at 03:36:49, adamk wrote:
> I don't think this should be strict...

Oops, deleted.

https://codereview.chromium.org/1286923002/diff/1/test/mjsunit/harmony/block-...
test/mjsunit/harmony/block-scoping-sloppy.js:282: //assertEquals(1,f.foo());
On 2015/08/12 at 03:36:49, adamk wrote:
> Another odd comment; is something broken?

Fixed, thanks.

[adamk, 2015-08-12 17:59:31]

lgtm

[commit-bot: I haz the power, 2015-08-12 18:16:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-08-12 18:16:40]

Dry run: This issue passed the CQ dry run.

[Dan Ehrenberg, 2015-08-12 18:40:55]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2015-08-12 18:41:11]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1286923002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1286923002/40001

[commit-bot: I haz the power, 2015-08-12 18:42:53]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-08-12 18:43:11]

Patchset 3 (id:??) landed as
https://crrev.com/e261540b9ee3182451faac7fcaba280b987cef10
Cr-Commit-Position: refs/heads/master@{#30140}