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.
This commit is contained in:
Shannon Booth 2024-11-14 05:50:17 +13:00 committed by Tim Flynn
commit 9b79a686eb
Notes: github-actions[bot] 2024-11-13 21:52:48 +00:00
326 changed files with 697 additions and 714 deletions

View file

@ -90,7 +90,7 @@ WebIDL::ExceptionOr<JS::NonnullGCPtr<PerformanceMark>> PerformanceMark::construc
}
// 2. Create a new PerformanceMark object (entry) with the current global object's realm.
return realm.heap().allocate<PerformanceMark>(realm, realm, name, start_time, duration, detail);
return realm.create<PerformanceMark>(realm, name, start_time, duration, detail);
}
FlyString const& PerformanceMark::entry_type() const