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.
35 lines
1 KiB
C++
35 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
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/Iterator.h>
|
|
#include <LibJS/Runtime/Object.h>
|
|
|
|
namespace JS {
|
|
|
|
// 27.1.4.3 Properties of Async-from-Sync Iterator Instances, https://tc39.es/ecma262/#sec-properties-of-async-from-sync-iterator-instances
|
|
class AsyncFromSyncIterator final : public Object {
|
|
JS_OBJECT(AsyncFromSyncIterator, Object);
|
|
|
|
public:
|
|
static AsyncFromSyncIterator* create(GlobalObject&, Iterator sync_iterator_record);
|
|
|
|
explicit AsyncFromSyncIterator(Realm&, Iterator sync_iterator_record);
|
|
virtual void initialize(Realm&) override;
|
|
virtual ~AsyncFromSyncIterator() override = default;
|
|
|
|
void visit_edges(Visitor& visitor) override;
|
|
|
|
Iterator& sync_iterator_record() { return m_sync_iterator_record; }
|
|
Iterator const& sync_iterator_record() const { return m_sync_iterator_record; }
|
|
|
|
private:
|
|
Iterator m_sync_iterator_record; // [[SyncIteratorRecord]]
|
|
};
|
|
|
|
}
|