From df616013cabfe255398868ab742d54e8558bff12 Mon Sep 17 00:00:00 2001
From: Lars Knoll <lars.knoll@qt.io>
Date: Tue, 15 May 2018 14:03:09 +0200
Subject: Cleanup handling of direct evals

There's no need to force lookups by name in an outer function
just because an inner function uses eval(). The lookup by name
is only required on the call context level, where eval() could
add new variables.

Change-Id: I8cad6d27524f496304342dfe1449ea913ef99fca
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
---
 src/qml/compiler/qv4compilercontext_p.h | 1 +
 1 file changed, 1 insertion(+)

(limited to 'src/qml/compiler/qv4compilercontext_p.h')

diff --git a/src/qml/compiler/qv4compilercontext_p.h b/src/qml/compiler/qv4compilercontext_p.h
index 95fca2c2c8..cce833f2ac 100644
--- a/src/qml/compiler/qv4compilercontext_p.h
+++ b/src/qml/compiler/qv4compilercontext_p.h
@@ -144,6 +144,7 @@ struct Context {
     int nRegisters = 0;
     int registerOffset = -1;
     bool hasDirectEval = false;
+    bool allVarsEscape = false;
     bool hasNestedFunctions = false;
     bool isStrict = false;
     bool isArrowFunction = false;
-- 
cgit v1.2.3