[cleanup] Use NewVariableProxy() instead of NewUnresolved where possible

Review URL: https://codereview.chromium.org/1386383003 Cr-Commit-Position: refs/heads/master@{#31202}

[cleanup] Use NewVariableProxy() instead of NewUnresolved where possible
Review URL: https://codereview.chromium.org/1386383003 Cr-Commit-Position: refs/heads/master@{#31202}
bef2fbcc · adamk · Commit bot · a0d119c7 · bef2fbcc
Commit bef2fbcc authored Oct 09, 2015 by adamk Committed by Commit bot Oct 09, 2015
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 2 deletions

parser.cc src/parser.cc +1 -2

No files found.
--- a/src/parser.cc
+++ b/src/parser.cc
@@ -4731,8 +4731,7 @@ ZoneList<Statement*>* Parser::ParseEagerFunctionBody(
        proxy, fvar_mode, scope_, RelocInfo::kNoPosition);
    scope_->DeclareFunctionVar(fvar_declaration);

-    VariableProxy* fproxy = scope_->NewUnresolved(factory(), function_name);
-    fproxy->BindTo(fvar);
+    VariableProxy* fproxy = factory()->NewVariableProxy(fvar);
    result->Set(kFunctionNameAssignmentIndex,
                factory()->NewExpressionStatement(
                    factory()->NewAssignment(fvar_init_op, fproxy,