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.
32 lines
780 B
C++
32 lines
780 B
C++
/*
|
|
* Copyright (c) 2020, Linus Groh <linusg@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/NativeFunction.h>
|
|
|
|
namespace JS {
|
|
|
|
class ArrayBufferConstructor final : public NativeFunction {
|
|
JS_OBJECT(ArrayBufferConstructor, NativeFunction);
|
|
|
|
public:
|
|
explicit ArrayBufferConstructor(Realm&);
|
|
virtual void initialize(Realm&) override;
|
|
virtual ~ArrayBufferConstructor() override = default;
|
|
|
|
virtual ThrowCompletionOr<Value> call() override;
|
|
virtual ThrowCompletionOr<Object*> construct(FunctionObject& new_target) override;
|
|
|
|
private:
|
|
virtual bool has_constructor() const override { return true; }
|
|
|
|
JS_DECLARE_NATIVE_FUNCTION(is_view);
|
|
|
|
JS_DECLARE_NATIVE_FUNCTION(symbol_species_getter);
|
|
};
|
|
|
|
}
|