e992a9f469
This is a continuation of the previous three commits. Now that create() receives the allocating realm, we can simply forward that to allocate(), which accounts for the majority of these changes. Additionally, we can get rid of the realm_from_global_object() in one place, with one more remaining in VM::throw_completion().
37 lines
1 KiB
C++
37 lines
1 KiB
C++
/*
|
|
* Copyright (c) 2021, David Tuin <davidot@serenityos.org>
|
|
* Copyright (c) 2022, Linus Groh <linusg@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibJS/Runtime/AsyncFromSyncIterator.h>
|
|
#include <LibJS/Runtime/AsyncFromSyncIteratorPrototype.h>
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
|
|
namespace JS {
|
|
|
|
AsyncFromSyncIterator* AsyncFromSyncIterator::create(Realm& realm, Iterator sync_iterator_record)
|
|
{
|
|
return realm.heap().allocate<AsyncFromSyncIterator>(realm, realm, sync_iterator_record);
|
|
}
|
|
|
|
AsyncFromSyncIterator::AsyncFromSyncIterator(Realm& realm, Iterator sync_iterator_record)
|
|
: Object(*realm.global_object().async_from_sync_iterator_prototype())
|
|
, m_sync_iterator_record(sync_iterator_record)
|
|
{
|
|
}
|
|
|
|
void AsyncFromSyncIterator::initialize(Realm& realm)
|
|
{
|
|
Object::initialize(realm);
|
|
}
|
|
|
|
void AsyncFromSyncIterator::visit_edges(Cell::Visitor& visitor)
|
|
{
|
|
Object::visit_edges(visitor);
|
|
visitor.visit(m_sync_iterator_record.iterator);
|
|
visitor.visit(m_sync_iterator_record.next_method);
|
|
}
|
|
|
|
}
|