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.
35 lines
1.1 KiB
C++
35 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
|
|
*/
|
|
|
|
#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(GlobalObject&) 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]]
|
|
};
|
|
|
|
}
|