LibWeb: Make DOMException take error message as a String

There was no need to use FlyString for error messages, and it just
caused a bunch of churn since these strings typically only existed
during the lifetime of the error.
This commit is contained in:
Andreas Kling 2024-10-12 20:56:21 +02:00 committed by Andreas Kling
commit 175f3febb8
Notes: github-actions[bot] 2024-10-12 19:15:13 +00:00
89 changed files with 464 additions and 462 deletions

View file

@ -12,20 +12,20 @@ namespace Web::WebIDL {
JS_DEFINE_ALLOCATOR(DOMException);
JS::NonnullGCPtr<DOMException> DOMException::create(JS::Realm& realm, FlyString const& name, FlyString const& message)
JS::NonnullGCPtr<DOMException> DOMException::create(JS::Realm& realm, FlyString name, String message)
{
return realm.heap().allocate<DOMException>(realm, realm, name, message);
return realm.heap().allocate<DOMException>(realm, realm, move(name), move(message));
}
JS::NonnullGCPtr<DOMException> DOMException::construct_impl(JS::Realm& realm, FlyString const& message, FlyString const& name)
JS::NonnullGCPtr<DOMException> DOMException::construct_impl(JS::Realm& realm, String message, FlyString name)
{
return realm.heap().allocate<DOMException>(realm, realm, name, message);
return realm.heap().allocate<DOMException>(realm, realm, move(name), move(message));
}
DOMException::DOMException(JS::Realm& realm, FlyString const& name, FlyString const& message)
DOMException::DOMException(JS::Realm& realm, FlyString name, String message)
: PlatformObject(realm)
, m_name(name)
, m_message(message)
, m_name(move(name))
, m_message(move(message))
{
}