Integrate registry_hash_store_contents with the rest of tracked prefs.

components/prefs/pref_filter.h

Index: components/prefs/pref_filter.h
diff --git a/components/prefs/pref_filter.h b/components/prefs/pref_filter.h
index 6ca2197618329bc12a2bd26bf4eaa3c0822b8138..dc649fcedc87abe190062c7cc40de2e30b9d64f1 100644
--- a/components/prefs/pref_filter.h
+++ b/components/prefs/pref_filter.h
@@ -51,6 +51,10 @@ class COMPONENTS_PREFS_EXPORT PrefFilter {
   // in-memory state.
   virtual void FilterSerializeData(
       base::DictionaryValue* pref_store_contents) = 0;
+
+  // Returns a callback which should be called once the pref_store is written.
+  virtual base::Closure GetPostSerializeCallback(
+      base::DictionaryValue* pref_store_contents) = 0;

[gab, 2016/08/03 18:19:34]

Instead of forcing the caller to call this in a particular order w.r.t.
FilterSerializeData, make the API:

  // Receives notification when the pref store is about to serialize data
  // contained in |pref_store_contents| to a string. Modifications to
  // |pref_store_contents| will be persisted to disk and also affect the
  // in-memory state. If the returned Callback is non-null, it will be
  // registered to be invoked synchronously after the next write (from the I/O
  // TaskRunner so it must not be bound to thread-unsafe member state).
  virtual base::Callback<void(bool success)> FilterSerializeData(
      base::DictionaryValue* pref_store_contents) = 0;

then it's up to the implementation to do things in the order that pleases it.

[proberge, 2016/08/04 00:13:45]

Done.

 };
 
 #endif  // COMPONENTS_PREFS_PREF_FILTER_H_