Use std::default_delete as the default deleter for scoped_ptr.

content/browser/service_worker/service_worker_process_manager.cc

Index: content/browser/service_worker/service_worker_process_manager.cc
diff --git a/content/browser/service_worker/service_worker_process_manager.cc b/content/browser/service_worker/service_worker_process_manager.cc
index a310bcc1770b5ca7ec279ad496b594db7ecaba50..fbeaead899ce545d1d1394445c92910546922b51 100644
--- a/content/browser/service_worker/service_worker_process_manager.cc
+++ b/content/browser/service_worker/service_worker_process_manager.cc
@@ -267,13 +267,13 @@ std::vector<int> ServiceWorkerProcessManager::SortProcessesForPattern(
 
 }  // namespace content
 
-namespace base {
+namespace std {
 // Destroying ServiceWorkerProcessManagers only on the UI thread allows the
 // member WeakPtr to safely guard the object's lifetime when used on that
 // thread.
-void DefaultDeleter<content::ServiceWorkerProcessManager>::operator()(
+void default_delete<content::ServiceWorkerProcessManager>::operator()(

[dcheng, 2015/11/16 18:22:59]

This is permitted by the C++ standard but probably looks a bit wonky. From
http://en.cppreference.com/w/cpp/language/extending_std:

"It is allowed to add template specializations for any standard library template
to the namespace std only if the declaration depends on a user-defined type and
the specialization satisfies all requirements for the original template, except
where such specializations are prohibited."

[danakj, 2015/11/16 22:19:03]

Oh.. thanks for the linky!

Why is this written as a function overload, but the previous one is written as a
template specialization?

[dcheng, 2015/11/17 17:08:42]

This is the definition of operator() in the previous template specialization.

[danakj, 2015/11/17 19:09:27]

Er, oh yes. Magnets..

     content::ServiceWorkerProcessManager* ptr) const {
   content::BrowserThread::DeleteSoon(
       content::BrowserThread::UI, FROM_HERE, ptr);
 }
-}  // namespace base
+}  // namespace std