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.
29 lines
799 B
C++
29 lines
799 B
C++
/*
|
|
* Copyright (c) 2021, Matthew Olsson <mattco@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/NativeFunction.h>
|
|
|
|
namespace JS {
|
|
|
|
// 27.3.1 %GeneratorFunction%, https://tc39.es/ecma262/#sec-generatorfunction-constructor
|
|
class GeneratorFunctionConstructor final : public NativeFunction {
|
|
JS_OBJECT(GeneratorFunctionConstructor, NativeFunction);
|
|
|
|
public:
|
|
explicit GeneratorFunctionConstructor(Realm&);
|
|
virtual void initialize(GlobalObject&) override;
|
|
virtual ~GeneratorFunctionConstructor() override = default;
|
|
|
|
virtual ThrowCompletionOr<Value> call() override;
|
|
virtual ThrowCompletionOr<Object*> construct(FunctionObject& new_target) override;
|
|
|
|
private:
|
|
bool has_constructor() const override { return true; }
|
|
};
|
|
|
|
}
|