Remove implicit conversions from scoped_refptr to T* in content/

Remove implicit conversions from scoped_refptr to T* in content/

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

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

[dcheng, 2014-11-12 23:09:43]

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

[nasko, 2014-11-12 23:18:25]

LGTM with a couple of nits.

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
File content/common/gpu/media/dxva_video_decode_accelerator.cc (right):

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
content/common/gpu/media/dxva_video_decode_accelerator.cc:332: hr =
decoder.device_->StretchRect(dest_surface, NULL, d3d_surface.get(), NULL,
nit: The params all fit on one line, so not sure why clang-format split them
like this.

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
content/common/gpu/media/dxva_video_decode_accelerator.cc:517: PLATFORM_FAILURE,
);
nit: Do we really need the extra space after ","? It isn't present in the rest
of the macros.

[dcheng, 2014-11-12 23:22:49]

How strongly do you feel about the formatting nits? =P

I think it's unlikely the space after comma thing in function-like macro calls
will change (and frankly, it's annoying to read either way). So IMO we should
just leave that.

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
File content/common/gpu/media/dxva_video_decode_accelerator.cc (right):

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
content/common/gpu/media/dxva_video_decode_accelerator.cc:332: hr =
decoder.device_->StretchRect(dest_surface, NULL, d3d_surface.get(), NULL,
On 2014/11/12 23:18:24, nasko wrote:
> nit: The params all fit on one line, so not sure why clang-format split them
> like this.

I'm pretty sure this is because we recently changed how clang-format prefers to
pack arguments at the call site =/

I don't really have a strong opinion here other than I'd prefer to avoid
fighting against clang-format. =)

https://codereview.chromium.org/719343002/diff/1/content/common/gpu/media/dxv...
content/common/gpu/media/dxva_video_decode_accelerator.cc:517: PLATFORM_FAILURE,
);
On 2014/11/12 23:18:24, nasko wrote:
> nit: Do we really need the extra space after ","? It isn't present in the rest
> of the macros.

Would prefer to avoid fighting clang-format here too. Frankly, I think it's ugly
either way.

[nasko, 2014-11-13 00:02:37]

On 2014/11/12 23:22:49, dcheng wrote:
> How strongly do you feel about the formatting nits? =P

Not as strongly since they come from clang-format. I do dislike some of its
formatting though :(. Just go ahead and ignore my nits.

[dcheng, 2014-11-13 00:05:31]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-11-13 00:06:53]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/719343002/1

[commit-bot: I haz the power, 2014-11-13 00:51:15]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-11-13 00:52:41]

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