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.
28 lines
750 B
C++
28 lines
750 B
C++
/*
|
|
* Copyright (c) 2021, Ali Mohammad Pur <mpfard@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/NativeFunction.h>
|
|
|
|
namespace Web::Bindings {
|
|
|
|
class WebAssemblyModuleConstructor : public JS::NativeFunction {
|
|
JS_OBJECT(WebAssemblyModuleConstructor, JS::NativeFunction);
|
|
|
|
public:
|
|
explicit WebAssemblyModuleConstructor(JS::Realm&);
|
|
virtual void initialize(JS::GlobalObject&) override;
|
|
virtual ~WebAssemblyModuleConstructor() override;
|
|
|
|
virtual JS::ThrowCompletionOr<JS::Value> call() override;
|
|
virtual JS::ThrowCompletionOr<JS::Object*> construct(JS::FunctionObject& new_target) override;
|
|
|
|
private:
|
|
virtual bool has_constructor() const override { return true; }
|
|
};
|
|
|
|
}
|