Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(128)

Side by Side Diff: test/mjsunit/strong/declaration-after-use.js

Issue 1213813003: [es6] Remove harmony-classes flag (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master
Patch Set: Remove empty flags field from json Created 5 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « test/mjsunit/strong/classes.js ('k') | test/mjsunit/strong/super.js » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 // Copyright 2015 the V8 project authors. All rights reserved. 1 // Copyright 2015 the V8 project authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 // Flags: --strong-mode --harmony_rest_parameters --harmony_arrow_functions --ha rmony_classes --harmony_computed-property_names 5 // Flags: --strong-mode --harmony-rest-parameters --harmony-arrow-functions
6 // Flags: --harmony-computed-property-names
6 7
7 // Note that it's essential for these tests that the reference is inside dead 8 // Note that it's essential for these tests that the reference is inside dead
8 // code (because we already produce ReferenceErrors for run-time unresolved 9 // code (because we already produce ReferenceErrors for run-time unresolved
9 // variables and don't want to confuse those with strong mode errors). But the 10 // variables and don't want to confuse those with strong mode errors). But the
10 // errors should *not* be inside lazy, unexecuted functions, since lazy parsing 11 // errors should *not* be inside lazy, unexecuted functions, since lazy parsing
11 // doesn't produce strong mode scoping errors). 12 // doesn't produce strong mode scoping errors).
12 13
13 // In addition, assertThrows will call eval and that changes variable binding 14 // In addition, assertThrows will call eval and that changes variable binding
14 // types (see e.g., UNBOUND_EVAL_SHADOWED). We can avoid unwanted side effects 15 // types (see e.g., UNBOUND_EVAL_SHADOWED). We can avoid unwanted side effects
15 // by wrapping the code to be tested inside an outer function. 16 // by wrapping the code to be tested inside an outer function.
(...skipping 234 matching lines...) Expand 10 before | Expand all | Expand 10 after
250 } 251 }
251 return new CInner(); 252 return new CInner();
252 } 253 }
253 } 254 }
254 (new COuter()).m().n(); 255 (new COuter()).m().n();
255 256
256 // Making sure the check which is supposed to prevent "object literal inside 257 // Making sure the check which is supposed to prevent "object literal inside
257 // computed property name references the class name" is not too generic: 258 // computed property name references the class name" is not too generic:
258 class C14 { m() { let obj = { n() { C14 } }; obj.n(); } }; (new C14()).m(); 259 class C14 { m() { let obj = { n() { C14 } }; obj.n(); } }; (new C14()).m();
259 })(); 260 })();
OLDNEW
« no previous file with comments | « test/mjsunit/strong/classes.js ('k') | test/mjsunit/strong/super.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698