[parsing] Fix maybe-assigned for top-level class declarations.

src/parsing/parser.h

Index: src/parsing/parser.h
diff --git a/src/parsing/parser.h b/src/parsing/parser.h
index 20c79371822276d08a8b1691a4855a9fb090ad59..8d873a22a74f259ae64cffd7b592191ca647b02f 100644
--- a/src/parsing/parser.h
+++ b/src/parsing/parser.h
@@ -824,20 +824,6 @@ class V8_EXPORT_PRIVATE Parser : public NON_EXPORTED_BASE(ParserBase<Parser>) {
     }
   }
 
-  // Pessimistically assume that top-level variables will be assigned.
-  //
-  // Top-level variables in a script can be accessed by other scripts or even
-  // become global properties. While this does not apply to top-level variables
-  // in a module (assuming they are not exported), we must still mark these as
-  // assigned because they might be accessed by a lazily parsed top-level
-  // function, which, for efficiency, we preparse without variable tracking.
-  V8_INLINE static void MarkTopLevelVariableAsAssigned(Scope* scope,
-                                                       VariableProxy* proxy) {
-    if (scope->is_script_scope() || scope->is_module_scope()) {
-      proxy->set_is_assigned();
-    }
-  }
-
   // Returns true if we have a binary expression between two numeric
   // literals. In that case, *x will be changed to an expression which is the
   // computed value.