mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 18:28:12 +00:00
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.
This commit is contained in:
parent
4c300cc5e8
commit
ecd163bdf1
315 changed files with 592 additions and 554 deletions
|
@ -23,7 +23,7 @@ class WebAssemblyObject final : public JS::Object {
|
|||
JS_OBJECT(WebAssemblyObject, JS::Object);
|
||||
|
||||
public:
|
||||
explicit WebAssemblyObject(JS::GlobalObject&);
|
||||
explicit WebAssemblyObject(JS::Realm&);
|
||||
virtual void initialize(JS::GlobalObject&) override;
|
||||
virtual ~WebAssemblyObject() override = default;
|
||||
|
||||
|
@ -69,7 +69,7 @@ class WebAssemblyMemoryObject final : public JS::Object {
|
|||
JS_OBJECT(WebAssemblyMemoryObject, JS::Object);
|
||||
|
||||
public:
|
||||
explicit WebAssemblyMemoryObject(JS::GlobalObject&, Wasm::MemoryAddress);
|
||||
WebAssemblyMemoryObject(JS::Realm&, Wasm::MemoryAddress);
|
||||
virtual ~WebAssemblyMemoryObject() override = default;
|
||||
|
||||
auto address() const { return m_address; }
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue