LibJS+LibWeb: Replace GlobalObject with Realm in object constructors

No functional changes - we can still very easily get to the global
object via `Realm::global_object()`. This is in preparation of moving
the intrinsics to the realm and no longer having to pass a global
object when allocating any object.
In a few (now, and many more in subsequent commits) places we get a
realm using `GlobalObject::associated_realm()`, this is intended to be
temporary. For example, create() functions will later receive the same
treatment and are passed a realm instead of a global object.

1 files changed, 2 insertions, 2 deletions

diff --git a/Userland/Libraries/LibJS/Runtime/GeneratorFunctionConstructor.cpp b/Userland/Libraries/LibJS/Runtime/GeneratorFunctionConstructor.cpp
index 950a413778..6fae3b8ad2 100644
--- a/Userland/Libraries/LibJS/Runtime/GeneratorFunctionConstructor.cpp
+++ b/Userland/Libraries/LibJS/Runtime/GeneratorFunctionConstructor.cpp
@@ -11,8 +11,8 @@
 
 namespace JS {
 
-GeneratorFunctionConstructor::GeneratorFunctionConstructor(GlobalObject& global_object)
-    : NativeFunction(*static_cast<Object*>(global_object.function_constructor()))
+GeneratorFunctionConstructor::GeneratorFunctionConstructor(Realm& realm)
+    : NativeFunction(static_cast<Object&>(*realm.global_object().function_constructor()))
 {
 }