v8/test/mjsunit/regress/regress-3138.js
adamk ed18aa65ea Remove support for legacy const, part 1
Now that ES2015 const has shipped, in Chrome 49, legacy const declarations
are no more. This lets us remove a bunch of code from many parts of the
codebase.

In this patch, I remove parser support for generating legacy const variables
from const declarations. This also removes the special "illegal declaration"
bit from Scope, which has ripples into all compiler backends.

Also gone are any tests which relied on legacy const declarations.

Note that we do still generate a Variable in mode CONST_LEGACY in one case:
function name bindings in sloppy mode. The likely fix there is to add a new
Variable::Kind for this case and handle it appropriately for stores in each
backend, but I leave that for a later patch to make this one completely
subtractive.

Review URL: https://codereview.chromium.org/1819123002

Cr-Commit-Position: refs/heads/master@{#35002}
2016-03-22 17:52:13 +00:00

31 lines
713 B
JavaScript

// Copyright 2014 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.
(function f(){
assertEquals("function", typeof f);
})();
(function f(){
var f; // Variable shadows function name.
assertEquals("undefined", typeof f);
})();
(function f(){
var f;
assertEquals("undefined", typeof f);
with ({}); // Force context allocation of both variable and function name.
})();
assertEquals("undefined", typeof f);
// var initialization is intercepted by with scope.
(function() {
var o = { a: 1 };
with (o) {
var a = 2;
}
assertEquals("undefined", typeof a);
assertEquals(2, o.a);
})();