c8a342a582
Compiler backends get their language mode from the current function, but should instead be deriving it from the current scope. This allows proper handling of the always-strictness of class declarations and expressions, and in particular the treatment of 'eval' calls in an extends clause as a strict eval. Also fix the parser's RecordEvalCall logic to only reach out to the DeclarationScope in sloppy mode, which fixes the strange case of a sloppy function thinking it contains a sloppy eval when in fact it contains only a strict eval. BUG=v8:4970 LOG=n Review-Url: https://codereview.chromium.org/1931003003 Cr-Commit-Position: refs/heads/master@{#36001}
16 lines
385 B
JavaScript
16 lines
385 B
JavaScript
// Copyright 2016 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
//
|
|
// Flags: --allow-natives-syntax
|
|
|
|
function g() {
|
|
var f;
|
|
class C extends eval("f = () => delete C; Array") {}
|
|
f();
|
|
}
|
|
|
|
assertThrows(g, SyntaxError);
|
|
%OptimizeFunctionOnNextCall(g);
|
|
assertThrows(g, SyntaxError);
|