Get rid of redundancies between load() and store() methods

It's silly that we have to mention each serializable data member in
both the load and the store methods.
Instead, whenever possible, forward these methods to a template that calls
the right function in the persistence backend based on its parameter.

Change-Id: I00e2dee8cdf55405f447cee27190bc97df8673e3
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

1 files changed, 7 insertions, 1 deletions

diff --git a/src/lib/corelib/buildgraph/rulenode.h b/src/lib/corelib/buildgraph/rulenode.h
index 50c625799..b502b7ac8 100644
--- a/src/lib/corelib/buildgraph/rulenode.h
+++ b/src/lib/corelib/buildgraph/rulenode.h
@@ -45,6 +45,7 @@
 #include "forward_decls.h"
 #include <language/forward_decls.h>
 #include <tools/dynamictypecheck.h>
+#include <tools/persistence.h>
 
 #include <unordered_map>
 
@@ -80,9 +81,14 @@ public:
     void removeOldInputArtifact(Artifact *artifact) { m_oldInputArtifacts.remove(artifact); }
 
     void load(PersistentPool &pool);
-    void store(PersistentPool &pool) const;
+    void store(PersistentPool &pool);
 
 private:
+    template<PersistentPool::OpType opType> void serializationOp(PersistentPool &pool)
+    {
+        pool.serializationOp<opType>(m_rule, m_oldInputArtifacts);
+    }
+
     ArtifactSet currentInputArtifacts() const;
 
     RuleConstPtr m_rule;