Shannon Booth 9b79a686eb LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T> ... The main motivation behind this is to remove JS specifics of the Realm from the implementation of the Heap. As a side effect of this change, this is a bit nicer to read than the previous approach, and in my opinion, also makes it a little more clear that this method is specific to a JavaScript Realm.		2024-11-13 16:51:44 -05:00
..
Instance.cpp	LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T>	2024-11-13 16:51:44 -05:00
Instance.h	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Instance.idl	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Memory.cpp	LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T>	2024-11-13 16:51:44 -05:00
Memory.h	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Memory.idl	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Module.cpp	LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T>	2024-11-13 16:51:44 -05:00
Module.h	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Module.idl	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Table.cpp	LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T>	2024-11-13 16:51:44 -05:00
Table.h	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
Table.idl	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
WebAssembly.cpp	LibJS+LibWeb: Use realm.create<T> instead of heap.allocate<T>	2024-11-13 16:51:44 -05:00
WebAssembly.h	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00
WebAssembly.idl	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00