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/language/resolvedfilecontext.h b/src/lib/corelib/language/resolvedfilecontext.h
index 6e6601c97..41b708676 100644
--- a/src/lib/corelib/language/resolvedfilecontext.h
+++ b/src/lib/corelib/language/resolvedfilecontext.h
@@ -42,6 +42,7 @@
 
 #include "forward_decls.h"
 #include "filecontextbase.h"
+#include <tools/persistence.h>
 
 namespace qbs {
 namespace Internal {
@@ -60,11 +61,16 @@ public:
     }
 
     void load(PersistentPool &pool);
-    void store(PersistentPool &pool) const;
+    void store(PersistentPool &pool);
 
 private:
     ResolvedFileContext() {}
     ResolvedFileContext(const FileContextBase &ctx);
+
+    template<PersistentPool::OpType opType> void serializationOp(PersistentPool &pool)
+    {
+        pool.serializationOp<opType>(m_filePath, m_jsExtensions, m_searchPaths, m_jsImports);
+    }
 };
 
 bool operator==(const ResolvedFileContext &a, const ResolvedFileContext &b);