Use OnceCallback on Mojo interfaces in //components/leak_detector

Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips `use_once_callback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
Review-Url: https://codereview.chromium.org/2864283002
Cr-Commit-Position: refs/heads/master@{#474330}
Committed: https://chromium.googlesource.com/chromium/src/+/dc5014660fb72764d23948e947b7b93ffcd49e9a

[tzik, 2017-05-08 08:47:10]

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

[commit-bot: I haz the power, 2017-05-08 08:47:46]

Dry run: CQ is trying da patch.

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

[commit-bot: I haz the power, 2017-05-08 10:39:11]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-08 10:39:11]

Dry run: This issue passed the CQ dry run.

[tzik, 2017-05-09 08:12:02]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips  flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

[tzik, 2017-05-09 08:12:26]

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

[commit-bot: I haz the power, 2017-05-09 08:13:06]

Dry run: CQ is trying da patch.

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

[tzik, 2017-05-09 08:17:44]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips  flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips  flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

[tzik, 2017-05-09 08:17:45]

tzik@chromium.org changed reviewers:
+ wfh@chromium.org

[commit-bot: I haz the power, 2017-05-09 09:09:25]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-09 09:09:25]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[tzik, 2017-05-09 10:59:01]

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

[commit-bot: I haz the power, 2017-05-09 10:59:25]

Dry run: CQ is trying da patch.

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

[tzik, 2017-05-09 11:07:22]

PTAL

[commit-bot: I haz the power, 2017-05-09 11:50:45]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-09 11:50:46]

Dry run: This issue passed the CQ dry run.

[tzik, 2017-05-11 09:10:43]

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

[commit-bot: I haz the power, 2017-05-11 09:11:30]

Dry run: CQ is trying da patch.

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

[commit-bot: I haz the power, 2017-05-11 11:04:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-11 11:04:23]

Dry run: Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[tzik, 2017-05-11 11:37:30]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips  flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips `use_once_callback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

[Will Harris, 2017-05-21 01:04:07]

lgtm

[tzik, 2017-05-24 15:41:01]

The CQ bit was checked by tzik@chromium.org

[commit-bot: I haz the power, 2017-05-24 15:41:22]

CQ is trying da patch.

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

[commit-bot: I haz the power, 2017-05-24 16:59:58]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1495640461800370,
"parent_rev": "c3a2fa143c3b2b867d74738b0978faf8818388a1", "commit_rev":
"dc5014660fb72764d23948e947b7b93ffcd49e9a"}

[commit-bot: I haz the power, 2017-05-24 17:00:13]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips `use_once_callback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018
==========

to

==========
Use OnceCallback on Mojo interfaces in //components/leak_detector

This CL flips `use_once_callback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//components/leak_detector starts using base::OnceCallback instead
of base::Callback on its return value handling.

The migration recipe was:
 - Convert pass-by-ref callback objects to pass-by-value.
 - Use std::move() to forward it to other consumer, or to invoke it
   with Callback::Run().
 - Handle wherever copies are required manually.
 - Check if the conversion doesn't change the semantics. As the transfer
   and invocation clobber the callback object, care about use-after-move.
   It's considered safe to consume almost scoped-out callback.

BUG=714018

Review-Url: https://codereview.chromium.org/2864283002
Cr-Commit-Position: refs/heads/master@{#474330}
Committed:
https://chromium.googlesource.com/chromium/src/+/dc5014660fb72764d23948e947b7...
==========

[commit-bot: I haz the power, 2017-05-24 17:00:14]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/dc5014660fb72764d23948e947b7...