b99cc7d050
This is a continuation of the previous two commits. As allocating a JS cell already primarily involves a realm instead of a global object, and we'll need to pass one to the allocate() function itself eventually (it's bridged via the global object right now), the create() functions need to receive a realm as well. The plan is for this to be the highest-level function that actually receives a realm and passes it around, AOs on an even higher level will use the "current realm" concept via VM::current_realm() as that's what the spec assumes; passing around realms (or global objects, for that matter) on higher AO levels is pointless and unlike for allocating individual objects, which may happen outside of regular JS execution, we don't need control over the specific realm that is being used there.
36 lines
878 B
C++
36 lines
878 B
C++
/*
|
|
* Copyright (c) 2020, Matthew Olsson <mattco@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/Object.h>
|
|
|
|
namespace JS {
|
|
|
|
class ArrayIterator final : public Object {
|
|
JS_OBJECT(ArrayIterator, Object);
|
|
|
|
public:
|
|
static ArrayIterator* create(Realm&, Value array, Object::PropertyKind iteration_kind);
|
|
|
|
explicit ArrayIterator(Value array, Object::PropertyKind iteration_kind, Object& prototype);
|
|
virtual ~ArrayIterator() override = default;
|
|
|
|
Value array() const { return m_array; }
|
|
Object::PropertyKind iteration_kind() const { return m_iteration_kind; }
|
|
size_t index() const { return m_index; }
|
|
|
|
private:
|
|
friend class ArrayIteratorPrototype;
|
|
|
|
virtual void visit_edges(Cell::Visitor&) override;
|
|
|
|
Value m_array;
|
|
Object::PropertyKind m_iteration_kind;
|
|
size_t m_index { 0 };
|
|
};
|
|
|
|
}
|