ecd163bdf1
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.
31 lines
824 B
C++
31 lines
824 B
C++
/*
|
|
* Copyright (c) 2021, Ali Mohammad Pur <mpfard@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/Object.h>
|
|
#include <LibWasm/AbstractMachine/AbstractMachine.h>
|
|
#include <LibWeb/Forward.h>
|
|
#include <LibWeb/WebAssembly/WebAssemblyInstanceObjectPrototype.h>
|
|
#include <LibWeb/WebAssembly/WebAssemblyObject.h>
|
|
|
|
namespace Web::Bindings {
|
|
|
|
class WebAssemblyModuleObject final : public JS::Object {
|
|
JS_OBJECT(WebAssemblyModuleObject, Object);
|
|
|
|
public:
|
|
explicit WebAssemblyModuleObject(JS::Realm&, size_t index);
|
|
virtual ~WebAssemblyModuleObject() override = default;
|
|
|
|
size_t index() const { return m_index; }
|
|
Wasm::Module const& module() const { return WebAssemblyObject::s_compiled_modules.at(m_index).module; }
|
|
|
|
private:
|
|
size_t m_index { 0 };
|
|
};
|
|
|
|
}
|