Remove implicit conversions from scoped_refptr to T* in components/password_manager

Remove implicit conversions from scoped_refptr to T* in components/password_manager

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

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

[dcheng, 2014-08-26 16:29:27]

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

[dcheng, 2014-08-26 16:29:27]

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().

[vabr (Chromium), 2014-08-26 16:47:38]

On 2014/08/26 16:29:27, dcheng (OOO) wrote:
> 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().

LGTM, Thanks for the explanation about multiple steps for making scoped_refptr
testable again.

Cheers,
Vaclav

[dcheng, 2014-08-26 16:53:10]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-08-26 16:54:27]

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

[commit-bot: I haz the power, 2014-08-26 17:50:54]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  ios_rel_device on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device/bu...)

[commit-bot: I haz the power, 2014-08-26 18:02:33]

Committed patchset #1 (1) as 50243a1bc5d4a4a55979233dde2476b74e6a91ef

[commit-bot: I haz the power, 2014-09-10 02:43:54]

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