ladybird/Userland/Libraries/LibWeb/WebAssembly/WebAssemblyTableObject.cpp

/*
 * Copyright (c) 2021, Ali Mohammad Pur <mpfard@serenityos.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include "WebAssemblyTablePrototype.h"
#include <LibWeb/WebAssembly/WebAssemblyTableObject.h>

namespace Web::Bindings {

WebAssemblyTableObject::WebAssemblyTableObject(JS::Realm& realm, Wasm::TableAddress address)
    : Object(Bindings::ensure_web_prototype<WebAssemblyTablePrototype>(realm, "WebAssemblyTablePrototype"))
    , m_address(address)
{
}

}
LibWeb+LibWasm: Implement the WebAssembly.Table object 2021-09-04 04:40:57 +04:30			`/*`
			`* Copyright (c) 2021, Ali Mohammad Pur <mpfard@serenityos.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#include "WebAssemblyTablePrototype.h"`
			`#include <LibWeb/WebAssembly/WebAssemblyTableObject.h>`

			`namespace Web::Bindings {`

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. 2022-08-16 00:20:49 +01:00			`WebAssemblyTableObject::WebAssemblyTableObject(JS::Realm& realm, Wasm::TableAddress address)`
LibWeb: Remove unecessary dependence on Window from WebAssembly classes These classes only needed Window to get at its realm. Pass a realm directly to construct WebAssembly classes. 2022-09-25 18:05:03 -06:00			`: Object(Bindings::ensure_web_prototype<WebAssemblyTablePrototype>(realm, "WebAssemblyTablePrototype"))`
LibWeb+LibWasm: Implement the WebAssembly.Table object 2021-09-04 04:40:57 +04:30			`, m_address(address)`
			`{`
			`}`

			`}`