From 05f41382bb527fbf2bb47340ad065b36f2e7409f Mon Sep 17 00:00:00 2001
From: Timothy Flynn <trflynn89@pm.me>
Date: Tue, 15 Nov 2022 11:24:59 -0500
Subject: 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.
---
 Userland/Libraries/LibDNS/Answer.h | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'Userland/Libraries/LibDNS/Answer.h')

diff --git a/Userland/Libraries/LibDNS/Answer.h b/Userland/Libraries/LibDNS/Answer.h
index a3d0ea7063..a8592ed749 100644
--- a/Userland/Libraries/LibDNS/Answer.h
+++ b/Userland/Libraries/LibDNS/Answer.h
@@ -94,7 +94,10 @@ struct AK::Formatter<DNS::RecordClass> : StandardFormatter {
 
 namespace IPC {
 
+template<>
 bool encode(Encoder&, DNS::Answer const&);
+
+template<>
 ErrorOr<void> decode(Decoder&, DNS::Answer&);
 
 }
-- 
cgit v1.2.3