ladybird/Userland/Libraries/LibWeb/NavigationTiming
Shannon Booth bad44f8fc9 LibWeb: Remove Bindings/Forward.h from LibWeb/Forward.h
This was resulting in a whole lot of rebuilding whenever a new IDL
interface was added.

Instead, just directly include the prototype in every C++ file which
needs it. While we only really need a forward declaration in each cpp
file; including the full prototype header (which itself only includes
LibJS/Object.h, which is already transitively brought in by
PlatformObject) - it seems like a small price to pay compared to what
feels like a full rebuild of LibWeb whenever a new IDL file is added.

Given all of these includes are only needed for the ::initialize
method, there is probably a smart way of avoiding this problem
altogether. I've considered both using some macro trickery or generating
these functions somehow instead.
2024-04-27 18:29:35 -04:00
..
EntryNames.cpp AK: Make "foo"_fly_string infallible 2023-08-07 16:03:27 +02:00
EntryNames.h AK: Make "foo"_fly_string infallible 2023-08-07 16:03:27 +02:00
PerformanceTiming.cpp LibWeb: Remove Bindings/Forward.h from LibWeb/Forward.h 2024-04-27 18:29:35 -04:00
PerformanceTiming.h LibWeb: Don't store WindowOrWorkerGlobalScopeMixin in Performance 2024-04-07 07:03:13 +02:00
PerformanceTiming.idl LibWeb: Add comments and missing items of various IDL files 2023-10-25 19:45:41 +02:00