Replaced usage of RefPtr::Release with std::move wraps.

Replaced usage of RefPtr::Release with std::move wraps.

Replaces many of the calls to RefPtr::Release with a std::move wrap,
which returns a RefPtr instead of a PassRefPtr. As the code currently
stands, most methods still expect a PassRefPtr and so the PassRefPtr
initialising constructor will be called passing in the RefPtr rvalue,
which calls RefPtr::Release anyway.

Future patches will see these variables changed from PassRefPtr to
RefPtr type then RefPtr::Release will not be used at all.

Does not handle RefPtr::Release calls in return statements that
default to move. This will be handled in a future patch.

NB patch also added new braces to if statements to satisfy presubmit
errors.

BUG=494719
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

[Bugs Nash, 2017-05-26 03:34:49]

Description was changed from

==========
Replaced usage of RefPtr::Release with std::move wraps.

Replaces many of the calls to RefPtr::Release with a std::move wrap,
which returns a RefPtr instead of a PassRefPtr. As the code currently
stands, most methods still expect a PassRefPtr and so the PassRefPtr
initialising constructor will be called passing in the RefPtr rvalue,
which calls RefPtr::Release anyway.

Future patches will see these variables changed from PassRefPtr to
RefPtr type then RefPtr::Release will not be used at all.

Does not handle RefPtr::Release calls in return statements that
default to move. This will be handled in a future patch.

NB patch also added new braces to if statements to satisfy presubmit
errors.

BUG=494719
==========

to

==========
Replaced usage of RefPtr::Release with std::move wraps.

Replaces many of the calls to RefPtr::Release with a std::move wrap,
which returns a RefPtr instead of a PassRefPtr. As the code currently
stands, most methods still expect a PassRefPtr and so the PassRefPtr
initialising constructor will be called passing in the RefPtr rvalue,
which calls RefPtr::Release anyway.

Future patches will see these variables changed from PassRefPtr to
RefPtr type then RefPtr::Release will not be used at all.

Does not handle RefPtr::Release calls in return statements that
default to move. This will be handled in a future patch.

NB patch also added new braces to if statements to satisfy presubmit
errors.

BUG=494719
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[Bugs Nash, 2017-05-26 03:34:56]

The CQ bit was checked by bugsnash@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-26 03:35:49]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Bugs Nash, 2017-05-26 03:43:47]

The CQ bit was unchecked by bugsnash@chromium.org