5dd5896588
This is a continuation of the previous commit. Calling initialize() is the first thing that's done after allocating a cell on the JS heap - and in the common case of allocating an object, that's where properties are assigned and intrinsics occasionally accessed. Since those are supposed to live on the realm eventually, this is another step into that direction.
38 lines
1.1 KiB
C++
38 lines
1.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(GlobalObject& global_object, Iterator sync_iterator_record)
|
|
{
|
|
auto& realm = *global_object.associated_realm();
|
|
return global_object.heap().allocate<AsyncFromSyncIterator>(global_object, 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);
|
|
}
|
|
|
|
}
|