mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-26 09:45:06 +02:00
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:
Notes:
github-actions[bot]
2024-11-13 21:52:48 +00:00
Author: https://github.com/shannonbooth Commit: https://github.com/LadybirdBrowser/ladybird/commit/9b79a686eb1 Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/2322 Reviewed-by: https://github.com/gmta
@@ -23,7 +23,7 @@ ImportMapParseResult::~ImportMapParseResult() = default;
|
||||
JS::NonnullGCPtr<ImportMapParseResult> ImportMapParseResult::create(JS::Realm& realm, ByteString const& input, URL::URL base_url)
|
||||
{
|
||||
// 1. Let result be an import map parse result whose import map is null and whose error to rethrow is null.
|
||||
auto result = realm.heap().allocate<ImportMapParseResult>(realm);
|
||||
auto result = realm.create<ImportMapParseResult>();
|
||||
|
||||
// 2. Parse an import map string given input and baseURL, catching any exceptions.
|
||||
auto import_map = parse_import_map_string(realm, input, base_url);
|
||||
|
||||
Reference in New Issue
Block a user