Make the distinction between "global frame" and "lexical frame" explicit. As a nice consequence, this lets us reduce GC churn since we no longer need to create a frame instance for the lexical frame at a callsite of either a function when the environment is frozen or a builtin function (since builtins cannot modify bindings in their lexical frame).

RELNOTES: None
PiperOrigin-RevId: 187495787

1 files changed, 1 insertions, 1 deletions

diff --git a/src/test/java/com/google/devtools/build/lib/syntax/EnvironmentTest.java b/src/test/java/com/google/devtools/build/lib/syntax/EnvironmentTest.java
index 36f8911fdf..44d8c1c6ab 100644
--- a/src/test/java/com/google/devtools/build/lib/syntax/EnvironmentTest.java
+++ b/src/test/java/com/google/devtools/build/lib/syntax/EnvironmentTest.java
@@ -280,7 +280,7 @@ public class EnvironmentTest extends EvaluationTestCase {
     parentEnv.update("a", 1);
     parentEnv.update("c", 2);
     parentEnv.update("b", 3);
-    Environment.Frame parentFrame = parentEnv.getGlobals();
+    Environment.GlobalFrame parentFrame = parentEnv.getGlobals();
     parentMutability.freeze();
     Mutability mutability = Mutability.create("testing");
     Environment env = Environment.builder(mutability)