Use OnceCallback on Mojo interfaces in //chrome/common/extensions

Use OnceCallback on Mojo interfaces in //chrome/common/extensions
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//chrome/common/extensions 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/2867013002
Cr-Commit-Position: refs/heads/master@{#470922}
Committed: https://chromium.googlesource.com/chromium/src/+/38559e13df29a3e51b30304bd78202350b8332b3

[tzik, 2017-05-08 07:09:34]

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

[commit-bot: I haz the power, 2017-05-08 07:10:09]

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 08:00:58]

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

[commit-bot: I haz the power, 2017-05-08 08:00:59]

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

[tzik, 2017-05-09 06:32:34]

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

[commit-bot: I haz the power, 2017-05-09 06:32:51]

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 06:34:27]

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //chrome/common/extensions
==========

to

==========
Use OnceCallback on Mojo interfaces in //chrome/common/extensions
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//chrome/common/extensions 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 07:02:03]

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

[tzik, 2017-05-09 09:10:04]

PTAL

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

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

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

Dry run: This issue passed the CQ dry run.

[sky, 2017-05-09 17:20:19]

LGTM

[tzik, 2017-05-11 08:39:55]

The CQ bit was checked by tzik@chromium.org

[tzik, 2017-05-11 08:39:55]

The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org
Link to the patchset: https://codereview.chromium.org/2867013002/#ps40001
(title: "rebase")

[commit-bot: I haz the power, 2017-05-11 08:40:37]

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 10:34:37]

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

[commit-bot: I haz the power, 2017-05-11 10:34:38]

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-11 10:43:35]

The CQ bit was checked by tzik@chromium.org

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

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:39:11]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1494499415555820,
"parent_rev": "79a55e4e9f3d76197bfa057d5a6792f59c36df34", "commit_rev":
"38559e13df29a3e51b30304bd78202350b8332b3"}

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

Description was changed from

==========
Use OnceCallback on Mojo interfaces in //chrome/common/extensions
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//chrome/common/extensions 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 //chrome/common/extensions
    
This CL flips `use_once_calback` flag on the Mojo code generator, and
fixes all compile errors after it. After this CL, Mojo interfaces in
//chrome/common/extensions 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/2867013002
Cr-Commit-Position: refs/heads/master@{#470922}
Committed:
https://chromium.googlesource.com/chromium/src/+/38559e13df29a3e51b30304bd782...
==========

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

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