summaryrefslogtreecommitdiff
path: root/Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp
diff options
context:
space:
mode:
authorLinus Groh <mail@linusgroh.de>2022-08-16 00:20:49 +0100
committerLinus Groh <mail@linusgroh.de>2022-08-23 13:58:30 +0100
commitecd163bdf1cbf8c9bca9e209a385a41ff5ca4f81 (patch)
tree3124e71500f8685c6bceff4c56b309f8f89ca58d /Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp
parent4c300cc5e864098f37239acec3c603a8c9079307 (diff)
downloadserenity-ecd163bdf1cbf8c9bca9e209a385a41ff5ca4f81.zip
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.
Diffstat (limited to 'Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp')
-rw-r--r--Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp b/Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp
index 9ea55d84f2..0488909712 100644
--- a/Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp
+++ b/Userland/Libraries/LibJS/Runtime/FunctionConstructor.cpp
@@ -19,8 +19,8 @@
namespace JS {
-FunctionConstructor::FunctionConstructor(GlobalObject& global_object)
- : NativeFunction(vm().names.Function.as_string(), *global_object.function_prototype())
+FunctionConstructor::FunctionConstructor(Realm& realm)
+ : NativeFunction(vm().names.Function.as_string(), *realm.global_object().function_prototype())
{
}