Rename request() method to getRequest().

third_party/WebKit/Source/core/loader/DocumentLoader.h

Index: third_party/WebKit/Source/core/loader/DocumentLoader.h
diff --git a/third_party/WebKit/Source/core/loader/DocumentLoader.h b/third_party/WebKit/Source/core/loader/DocumentLoader.h
index c36f01a1089a305f613972c88a4d0c57f8b6607c..95929eb3763b40a0b9a6819446df23a441774254 100644
--- a/third_party/WebKit/Source/core/loader/DocumentLoader.h
+++ b/third_party/WebKit/Source/core/loader/DocumentLoader.h
@@ -93,7 +93,7 @@ class CORE_EXPORT DocumentLoader
 
   const ResourceRequest& originalRequest() const;
 
-  const ResourceRequest& request() const;
+  const ResourceRequest& getRequest() const;

[yhirano, 2016/12/16 14:52:37]

Would it be reasonable to make this function inline and keep the name?

[Łukasz Anforowicz, 2016/12/16 17:15:03]

This wouldn't have helped with the problem described in the linked bug and the
CL description - after a naive automated rename, we would still end up with the
same identifier (|Request|) for both a type and a method - such situation leads
to build errors after the automated rename.  This CL will unblock (*) the
automatic rename.

(*) Well, unblock as far as |request| vs |Request| conflict goes.  There are
other issues that cause build errors after the automatic rename.  We are trying
to systematically work through these issues.

 
   ResourceFetcher* fetcher() const { return m_fetcher.get(); }