ladybird/Libraries/LibWeb/Fetch/Infrastructure/ConnectionTimingInfo.cpp

/*
 * Copyright (c) 2022, Linus Groh <linusg@serenityos.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibGC/Heap.h>
#include <LibJS/Runtime/VM.h>
#include <LibWeb/Fetch/Infrastructure/ConnectionTimingInfo.h>

namespace Web::Fetch::Infrastructure {

GC_DEFINE_ALLOCATOR(ConnectionTimingInfo);

ConnectionTimingInfo::ConnectionTimingInfo() = default;

GC::Ref<ConnectionTimingInfo> ConnectionTimingInfo::create(JS::VM& vm)
{
    return vm.heap().allocate<ConnectionTimingInfo>();
}

}
LibWeb: Implement 'connection timing info' struct 2022-10-13 14:19:32 -03:00			`/*`
			`* Copyright (c) 2022, Linus Groh <linusg@serenityos.org>`
			`*`
			`* 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-14 12:01:23 -03:00			`#include <LibGC/Heap.h>`
LibWeb: Implement 'connection timing info' struct 2022-10-13 14:19:32 -03:00			`#include <LibJS/Runtime/VM.h>`
			`#include <LibWeb/Fetch/Infrastructure/ConnectionTimingInfo.h>`

			`namespace Web::Fetch::Infrastructure {`

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-14 12:01:23 -03:00			`GC_DEFINE_ALLOCATOR(ConnectionTimingInfo);`
LibWeb: Put most LibWeb GC objects in type-specific heap blocks With this change, we now have ~1200 CellAllocators across both LibJS and LibWeb in a normal WebContent instance. This gives us a minimum heap size of 4.7 MiB in the scenario where we only have one cell allocated per type. Of course, in practice there will be many more of each type, so the effective overhead is quite a bit smaller than that in practice. I left a few types unconverted to this mechanism because I got tired of doing this. :^) 2023-11-19 15:47:52 -03:00
LibWeb: Implement 'connection timing info' struct 2022-10-13 14:19:32 -03:00			`ConnectionTimingInfo::ConnectionTimingInfo() = default;`

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-14 12:01:23 -03:00			`GC::Ref<ConnectionTimingInfo> ConnectionTimingInfo::create(JS::VM& vm)`
LibWeb: Implement 'connection timing info' struct 2022-10-13 14:19:32 -03:00			`{`
LibJS+LibWeb: Rename Heap::allocate_without_realm to Heap::allocate Now that the heap has no knowledge about a JavaScript realm and is purely for managing the memory of the heap, it does not make sense to name this function to say that it is a non-realm variant. 2024-11-13 14:13:46 -03:00			`return vm.heap().allocate<ConnectionTimingInfo>();`
LibWeb: Implement 'connection timing info' struct 2022-10-13 14:19:32 -03:00			`}`

			`}`