Remove implicit conversions from scoped_refptr to T* in chrome/browser/browsing_data/

Remove implicit conversions from scoped_refptr to T* in chrome/browser/browsing_data/

This patch was generated by running the rewrite_scoped_refptr clang tool
on a Linux build.

BUG=110610
Committed: https://crrev.com/f9f817541db4f5a660ff8c52ab478574db8bb1ef
Cr-Commit-Position: refs/heads/master@{#291996}

[dcheng, 2014-08-26 18:11:35]

dcheng@chromium.org changed reviewers:
+ michaeln@chromium.org

[dcheng, 2014-08-26 18:11:35]

(Sorry, sole non-EMEA owner of many directories)

Unfortunately, we can't make scoped_refptr testable until the conversion
operator has been removed. While it would be possible to disable the conversion
operator and make it testable in the same patch, the automated tool tries to
skip rewriting code where manual cleanups would be useful. This includes things
like:

// What if ReturnsScopedRefPtr() creates a new object internally?
if (ReturnsScopedRefPtr())

Foo* Bar() {
  const scoped_refptr<Foo>& f = ReturnsScopedRefPtr();
  return f;  // Does the return type need to be rewritten? Or is .get() safe?
}

Doing this in one patch would make catching some of these instances (in
particular, a boolean test on a temporary scoped_refptr) more difficult. As a
result, the work is being split into several steps:
Step 1: Rewrite all implicit conversions to be explicit (or rewrite the receiver
type to scoped_refptr<T>, if the tool believes the conversion to be unsafe).
Step 2: Once a platform compiles cleanly without the conversion operator, #ifdef
the conversion operator out.
Step 3: Make scoped_refptr testable on that platform.
Step 4: Remove unnecessary calls to .get().

[michaeln, 2014-08-26 20:43:58]

r/s lgtm

> (Sorry, sole non-EMEA owner of many directories)

i don't know how i got to be owner of this browsing data stuff to tell you the
truth?

> // What if ReturnsScopedRefPtr() creates a new object internally?
> if (ReturnsScopedRefPtr())
> 
> Foo* Bar() {
>   const scoped_refptr<Foo>& f = ReturnsScopedRefPtr();
>   return f;  // Does the return type need to be rewritten? Or is .get() safe?
> }

btw, please don't write code that looks like ^^^

[dcheng, 2014-08-26 20:51:20]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-08-26 20:52:24]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dcheng@chromium.org/503363003/1

[commit-bot: I haz the power, 2014-08-26 22:16:37]

Committed patchset #1 (1) as a7884e17812ecb254cd14f30b49d74e084f658fd

[commit-bot: I haz the power, 2014-09-10 02:46:07]

Patchset 1 (id:??) landed as
https://crrev.com/f9f817541db4f5a660ff8c52ab478574db8bb1ef
Cr-Commit-Position: refs/heads/master@{#291996}