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.
39 lines
1.3 KiB
C++
39 lines
1.3 KiB
C++
/*
|
|
* Copyright (c) 2022, Idan Horowitz <idan.horowitz@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
#include <LibJS/Runtime/Intl/Segments.h>
|
|
#include <LibJS/Runtime/Intl/SegmentsPrototype.h>
|
|
|
|
namespace JS::Intl {
|
|
|
|
// 18.5.1 CreateSegmentsObject ( segmenter, string ), https://tc39.es/ecma402/#sec-createsegmentsobject
|
|
Segments* Segments::create(GlobalObject& global_object, Segmenter& segmenter, Utf16String string)
|
|
{
|
|
auto& realm = *global_object.associated_realm();
|
|
// 1. Let internalSlotsList be « [[SegmentsSegmenter]], [[SegmentsString]] ».
|
|
// 2. Let segments be OrdinaryObjectCreate(%SegmentsPrototype%, internalSlotsList).
|
|
// 3. Set segments.[[SegmentsSegmenter]] to segmenter.
|
|
// 4. Set segments.[[SegmentsString]] to string.
|
|
// 5. Return segments.
|
|
return global_object.heap().allocate<Segments>(global_object, realm, segmenter, move(string));
|
|
}
|
|
|
|
// 18.5 Segments Objects, https://tc39.es/ecma402/#sec-segments-objects
|
|
Segments::Segments(Realm& realm, Segmenter& segmenter, Utf16String string)
|
|
: Object(*realm.global_object().intl_segments_prototype())
|
|
, m_segments_segmenter(segmenter)
|
|
, m_segments_string(move(string))
|
|
{
|
|
}
|
|
|
|
void Segments::visit_edges(Cell::Visitor& visitor)
|
|
{
|
|
Base::visit_edges(visitor);
|
|
visitor.visit(&m_segments_segmenter);
|
|
}
|
|
|
|
}
|