[Popular Sites] Split PopularSites interface and PopularSitesImpl

chrome/browser/android/ntp/popular_sites.h

Index: chrome/browser/android/ntp/popular_sites.h
diff --git a/chrome/browser/android/ntp/popular_sites.h b/chrome/browser/android/ntp/popular_sites.h
index 07d37306ead33594c6c5ba696c302dedfe71e162..1f83cf2136e30e74b48c099bfcaa26386a80a274 100644
--- a/chrome/browser/android/ntp/popular_sites.h
+++ b/chrome/browser/android/ntp/popular_sites.h
@@ -13,13 +13,13 @@
 class Profile;
 
 namespace ntp_tiles {
-class PopularSites;
+class PopularSitesImpl;
 }  // namespace ntp_tiles
 
 // TODO(sfiera): move to chrome_popular_sites.h
 class ChromePopularSites {
  public:
-  static std::unique_ptr<ntp_tiles::PopularSites> NewForProfile(
+  static std::unique_ptr<ntp_tiles::PopularSitesImpl> NewForProfile(

[sfiera, 2016/12/13 10:53:57]

Should the factory be promising that it creates a particular implementation?

[mastiz, 2016/12/13 12:14:56]

The alternative would be to move the two remaining functions (local_path,
LastURL) to the interface. I didn't like this idea before, but I'm not convinced
anymore. WDYT?

[sfiera, 2016/12/13 12:30:27]

Hmm. They do feel like implementation details, but I think they are only used
for diagnostics in the webui, right? I think I'm OK with them being in the
interface for that purpose.

In the future, maybe the interface can have just base::Value DebugInfo().

[mastiz, 2016/12/13 12:31:53]

Went ahead and exported a new patchset following this suggestion. I actually
think it's cleaner, and it shouldn't bother future tests much.

       Profile* profile);
 
  private: