mac: Replace base::mac::ScopedCFTypeRef with base::ScopedCFTypeRef.

chrome/browser/extensions/api/file_system/file_system_api.cc

Index: chrome/browser/extensions/api/file_system/file_system_api.cc
diff --git a/chrome/browser/extensions/api/file_system/file_system_api.cc b/chrome/browser/extensions/api/file_system/file_system_api.cc
index a2a5182967813a4ec0c247266a62dda475836f44..235b770ad55e5c4f4119d7599ddf26543c7cbc5c 100644
--- a/chrome/browser/extensions/api/file_system/file_system_api.cc
+++ b/chrome/browser/extensions/api/file_system/file_system_api.cc
@@ -85,12 +85,8 @@ const int kWhitelistedPaths[] = {
 // Retrieves the localized display name for the base name of the given path.
 // If the path is not localized, this will just return the base name.
 std::string GetDisplayBaseName(const base::FilePath& path) {
-  base::mac::ScopedCFTypeRef<CFURLRef> url(
-      CFURLCreateFromFileSystemRepresentation(
-          NULL,
-          (const UInt8*)path.value().c_str(),
-          path.value().length(),
-          true));
+  base::ScopedCFTypeRef<CFURLRef> url(CFURLCreateFromFileSystemRepresentation(
+      NULL, (const UInt8*)path.value().c_str(), path.value().length(), true));

[Mark Mentovai, 2013/06/21 20:29:40]

The automatic formatter has done this a handful of times, moving arguments that
had been on separate lines into a single line. In some cases it’s OK, but in
others, I think having the arguments on their own lines is more readable. In
this case, the arguments are harder to spot just by looking for commas because
there’s a lot of funny punctuation going on on this line, so I think the line
breaks were helpful.

[Nico, 2013/06/21 21:09:06]

I think the rule clang-format uses is "if all parameters fit on a single line
put them on a single line, else use one line per argument" (with
-style=Chromium. with -style=Google, it packs them as tightly as it can.)

   if (!url)
     return path.BaseName().value();