v8/test/mjsunit/es6/block-eval-var-over-let.js
adamk 83b63c308a Sloppy eval declarations should not shadow lexical function declarations
This was being allowed due to the use of BindingFlags instead of VariableMode
to determine whether a looked-up binding was lexical. Because function
declarations are hoisted, they never need hole checks, and so were being
miscategorized as non-lexical.

This patch augments Context::Lookup with a VariableMode out param, which
allows this check to determine precisely whether the binding is lexical.

BUG=v8:4454, v8:5256

Review-Url: https://codereview.chromium.org/2206483004
Cr-Commit-Position: refs/heads/master@{#38260}
2016-08-02 20:27:38 +00:00

156 lines
2.7 KiB
JavaScript

// Copyright 2015 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.
// Var-let conflict in a function throws, even if the var is in an eval
// Throws at the top level of a function
assertThrows(function() {
let x = 1;
eval('var x');
}, SyntaxError);
// If the eval is in its own block scope, throws
assertThrows(function() {
let y = 1;
{ eval('var y'); }
}, SyntaxError);
// If the let is in its own block scope, with the eval, throws
assertThrows(function() {
{
let x = 1;
eval('var x');
}
}, SyntaxError);
// Legal if the let is no longer visible
assertDoesNotThrow(function() {
{
let x = 1;
}
eval('var x');
});
// All the same works for const:
// Throws at the top level of a function
assertThrows(function() {
const x = 1;
eval('var x');
}, SyntaxError);
// If the eval is in its own block scope, throws
assertThrows(function() {
const y = 1;
{ eval('var y'); }
}, SyntaxError);
// If the const is in its own block scope, with the eval, throws
assertThrows(function() {
{
const x = 1;
eval('var x');
}
}, SyntaxError);
// Legal if the const is no longer visible
assertDoesNotThrow(function() {
{
const x = 1;
}
eval('var x');
});
// The same should work for lexical function declarations:
// If the const is in its own block scope, with the eval, throws
assertThrows(function() {
{
function x() {}
eval('var x');
}
}, SyntaxError);
// If the eval is in its own block scope, throws
assertThrows(function() {
{
function y() {}
{ eval('var y'); }
}
}, SyntaxError);
// In global scope
let caught = false;
try {
let z = 1;
eval('var z');
} catch (e) {
caught = true;
}
assertTrue(caught);
// Let declarations beyond a function boundary don't conflict
caught = false;
try {
let a = 1;
(function() {
eval('var a');
})();
} catch (e) {
caught = true;
}
assertFalse(caught);
// var across with doesn't conflict
caught = false;
try {
(function() {
with ({x: 1}) {
eval("var x");
}
})();
} catch (e) {
caught = true;
}
assertFalse(caught);
// var can still conflict with let across a with
caught = false;
try {
(function() {
let x;
with ({x: 1}) {
eval("var x");
}
})();
} catch (e) {
caught = true;
}
assertTrue(caught);
// Functions declared in eval also conflict
caught = false
try {
(function() {
{
let x = 1;
eval('function x() {}');
}
})();
} catch (e) {
caught = true;
}
assertTrue(caught);
caught = false
try {
(function() {
{
let x = 1;
eval('{ function x() {} }');
}
})();
} catch (e) {
caught = true;
}
assertFalse(caught);