ladybird/Libraries/LibGC/ConservativeVector.cpp

/*
 * Copyright (c) 2024, Andreas Kling <andreas@ladybird.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibGC/ConservativeVector.h>
#include <LibGC/Heap.h>

namespace GC {

ConservativeVectorBase::ConservativeVectorBase(Heap& heap)
    : m_heap(&heap)
{
    m_heap->did_create_conservative_vector({}, *this);
}

ConservativeVectorBase::~ConservativeVectorBase()
{
    m_heap->did_destroy_conservative_vector({}, *this);
}

}
LibJS: Add ConservativeVector<T> This works very similarly to MarkedVector<T>, but instead of expecting T to be Value or a GC-allocated pointer type, T can be anything. Every pointer-sized value in the vector's storage will be checked during conservative root scanning. In other words, this allows you to put something like this in a ConservativeVector<Foo> and it will be protected from GC: struct Foo { i64 number; Value some_value; GCPtr<Object> some_object; }; 2024-02-22 13:18:31 +01:00			`/*`
Meta: Update my e-mail address everywhere 2024-10-04 13:19:50 +02:00			`* Copyright (c) 2024, Andreas Kling <andreas@ladybird.org>`
LibJS: Add ConservativeVector<T> This works very similarly to MarkedVector<T>, but instead of expecting T to be Value or a GC-allocated pointer type, T can be anything. Every pointer-sized value in the vector's storage will be checked during conservative root scanning. In other words, this allows you to put something like this in a ConservativeVector<Foo> and it will be protected from GC: struct Foo { i64 number; Value some_value; GCPtr<Object> some_object; }; 2024-02-22 13:18:31 +01:00			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root 2024-11-15 04:01:23 +13:00			`#include <LibGC/ConservativeVector.h>`
			`#include <LibGC/Heap.h>`
LibJS: Add ConservativeVector<T> This works very similarly to MarkedVector<T>, but instead of expecting T to be Value or a GC-allocated pointer type, T can be anything. Every pointer-sized value in the vector's storage will be checked during conservative root scanning. In other words, this allows you to put something like this in a ConservativeVector<Foo> and it will be protected from GC: struct Foo { i64 number; Value some_value; GCPtr<Object> some_object; }; 2024-02-22 13:18:31 +01:00
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root 2024-11-15 04:01:23 +13:00			`namespace GC {`
LibJS: Add ConservativeVector<T> This works very similarly to MarkedVector<T>, but instead of expecting T to be Value or a GC-allocated pointer type, T can be anything. Every pointer-sized value in the vector's storage will be checked during conservative root scanning. In other words, this allows you to put something like this in a ConservativeVector<Foo> and it will be protected from GC: struct Foo { i64 number; Value some_value; GCPtr<Object> some_object; }; 2024-02-22 13:18:31 +01:00
			`ConservativeVectorBase::ConservativeVectorBase(Heap& heap)`
			`: m_heap(&heap)`
			`{`
			`m_heap->did_create_conservative_vector({}, *this);`
			`}`

			`ConservativeVectorBase::~ConservativeVectorBase()`
			`{`
			`m_heap->did_destroy_conservative_vector({}, *this);`
			`}`

			`}`