9b79a686eb
The main motivation behind this is to remove JS specifics of the Realm from the implementation of the Heap. As a side effect of this change, this is a bit nicer to read than the previous approach, and in my opinion, also makes it a little more clear that this method is specific to a JavaScript Realm.
48 lines
1.4 KiB
C++
48 lines
1.4 KiB
C++
/*
|
|
* Copyright (c) 2021-2023, Linus Groh <linusg@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
#include <LibJS/Runtime/NativeFunction.h>
|
|
#include <LibJS/Runtime/Promise.h>
|
|
#include <LibJS/Runtime/PromiseResolvingFunction.h>
|
|
|
|
namespace JS {
|
|
|
|
JS_DEFINE_ALLOCATOR(AlreadyResolved);
|
|
JS_DEFINE_ALLOCATOR(PromiseResolvingFunction);
|
|
|
|
NonnullGCPtr<PromiseResolvingFunction> PromiseResolvingFunction::create(Realm& realm, Promise& promise, AlreadyResolved& already_resolved, FunctionType function)
|
|
{
|
|
return realm.create<PromiseResolvingFunction>(promise, already_resolved, move(function), realm.intrinsics().function_prototype());
|
|
}
|
|
|
|
PromiseResolvingFunction::PromiseResolvingFunction(Promise& promise, AlreadyResolved& already_resolved, FunctionType native_function, Object& prototype)
|
|
: NativeFunction(prototype)
|
|
, m_promise(promise)
|
|
, m_already_resolved(already_resolved)
|
|
, m_native_function(move(native_function))
|
|
{
|
|
}
|
|
|
|
void PromiseResolvingFunction::initialize(Realm& realm)
|
|
{
|
|
Base::initialize(realm);
|
|
define_direct_property(vm().names.length, Value(1), Attribute::Configurable);
|
|
}
|
|
|
|
ThrowCompletionOr<Value> PromiseResolvingFunction::call()
|
|
{
|
|
return m_native_function(vm(), m_promise, m_already_resolved);
|
|
}
|
|
|
|
void PromiseResolvingFunction::visit_edges(Cell::Visitor& visitor)
|
|
{
|
|
Base::visit_edges(visitor);
|
|
visitor.visit(m_promise);
|
|
visitor.visit(m_already_resolved);
|
|
}
|
|
|
|
}
|