mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 04:37:34 +00:00
Userland: Properly define IPC::encode and IPC::decode specializations
In order to avoid the base encode/decode methods from being used (and failing a static assertion), we must be sure to declare/define the custom type implementations as template specializations. After this, LibIPC is no longer sensitive to include order.
This commit is contained in:
parent
b1ea418d14
commit
05f41382bb
25 changed files with 75 additions and 2 deletions
|
@ -347,6 +347,7 @@ Optional<Core::DateTime> parse_date_time(StringView date_string)
|
|||
|
||||
}
|
||||
|
||||
template<>
|
||||
bool IPC::encode(Encoder& encoder, Web::Cookie::ParsedCookie const& cookie)
|
||||
{
|
||||
encoder << cookie.name;
|
||||
|
@ -362,6 +363,7 @@ bool IPC::encode(Encoder& encoder, Web::Cookie::ParsedCookie const& cookie)
|
|||
return true;
|
||||
}
|
||||
|
||||
template<>
|
||||
ErrorOr<void> IPC::decode(Decoder& decoder, Web::Cookie::ParsedCookie& cookie)
|
||||
{
|
||||
TRY(decoder.decode(cookie.name));
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue