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

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

Issue 961823002: Fix issue with class name TDZ in computed property names (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master
Patch Set: Comment out strong test Created 5 years, 9 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/harmony/computed-property-names-classes.js ('k') | no next file » | 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 --ha rmony_classes --harmony-computed-property-names
6 6
7 // Note that it's essential for these tests that the reference is inside dead 7 // 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 8 // 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 9 // 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 10 // errors should *not* be inside lazy, unexecuted functions, since lazy parsing
(...skipping 162 matching lines...) Expand 10 before | Expand all | Expand 10 after
173 var1, var2a, var2b, var2c; 173 var1, var2a, var2b, var2c;
174 } 174 }
175 175
176 (function eval1() { 176 (function eval1() {
177 let var7 = 0; // Declaration position will be something large. 177 let var7 = 0; // Declaration position will be something large.
178 // But use position will be something small, however, this is not an error, 178 // But use position will be something small, however, this is not an error,
179 // since the use is inside an eval scope. 179 // since the use is inside an eval scope.
180 eval("var7;"); 180 eval("var7;");
181 })(); 181 })();
182 182
183 class C1 { constructor() { C1; } }; new C1(); 183 // https://code.google.com/p/v8/issues/detail?id=3927
184 let C2 = class C3 { constructor() { C3; } }; new C2(); 184 // class C1 { constructor() { C1; } }; new C1();
185 // let C2 = class C3 { constructor() { C3; } }; new C2();
185 186
186 class C4 { method() { C4; method; } }; new C4(); 187 // class C4 { method() { C4; method; } }; new C4();
187 let C5 = class C6 { method() { C6; method; } }; new C5(); 188 // let C5 = class C6 { method() { C6; method; } }; new C5();
188 })(); 189 })();
OLDNEW
« no previous file with comments | « test/mjsunit/harmony/computed-property-names-classes.js ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698