Replace deprecated base::NonThreadSafe in /content/browser/speech in favor of SequenceChecker.

Replace deprecated base::NonThreadSafe in /content/browser/speech in favor of SequenceChecker.

Note to crash team: This CL is a refactor and has no intended behavior change.

This change was scripted by https://crbug.com/676387#c84.

If you're wondering why there's a second wave of this, the first version of the
script handled "NON_EXPORTED_BASE(public base::NonThreadSafe)" but not
"public NON_EXPORTED_BASE(base::NonThreadSafe)"...

Note-worthy for the reviewer:
 * SequenceChecker enforces thread-safety but not thread-affinity!
   If the classes that were updated are thread-affine (use thread local
   storage or a third-party API that does) they should be migrated to
   ThreadChecker instead.
 * ~NonThreadSafe() used to implicitly check in its destructor
   ~Sequence/ThreadChecker() doesn't by design. To keep this CL a
   no-op, an explicit check was added to the destructor of migrated
   classes.
 * NonThreadSafe used to provide access to subclasses, as such
   the |sequence_checker_| member was made protected rather than
   private where necessary.

BUG=676387
This CL was uploaded by git cl split.

R=tommi@chromium.org

Review-Url: https://codereview.chromium.org/2919993002
Cr-Commit-Position: refs/heads/master@{#476748}
Committed: https://chromium.googlesource.com/chromium/src/+/2510d3fbc38be38f5c8cd870dc9d7329d0f43a99

[gab, 2017-06-02 18:05:34]

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

[gab, 2017-06-02 18:05:36]

Hi, this is an automated change made by https://crbug.com/676387#c84 and sharded
across directories for OWNERS.

No human has looked at this specific output yet, see cl description for things
to watch for.

If it LGTY, please CQ.

Thanks!
Gab

[commit-bot: I haz the power, 2017-06-02 18:06:34]

Dry run: CQ is trying da patch.

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

[gab, 2017-06-02 19:05:18]

gab@chromium.org changed reviewers:
+ creis@chromium.org

[gab, 2017-06-02 19:05:18]

Charlie any chance you're familiar enough with this code to review ahead of
"tommi (sloooow)" who's the sole owner in speech..?

Basically just need to look if it uses any thread-affine APIs.

This is one of the last few CLs blocking getting rid of base::NonThreadSafe :)

Thanks!

[tommi (sloooow) - chröme, 2017-06-02 19:08:19]

lgtm

[gab, 2017-06-02 19:14:38]

The CQ bit was unchecked by gab@chromium.org

[gab, 2017-06-02 19:14:41]

The CQ bit was checked by gab@chromium.org

[commit-bot: I haz the power, 2017-06-02 19:15:10]

CQ is trying da patch.

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

[gab, 2017-06-02 19:15:38]

On 2017/06/02 19:08:19, tommi (sloooow) - chröme wrote:
> lgtm

Awesome, thanks for Friday night review :)

[commit-bot: I haz the power, 2017-06-02 19:20:21]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1496430881661650, "parent_rev":
"e5d889dd030151c5c2ae62b5c5be42ea07526938", "commit_rev":
"2510d3fbc38be38f5c8cd870dc9d7329d0f43a99"}

[commit-bot: I haz the power, 2017-06-02 19:20:31]

Description was changed from

==========
Replace deprecated base::NonThreadSafe in /content/browser/speech in favor of
SequenceChecker.

Note to crash team: This CL is a refactor and has no intended behavior change.

This change was scripted by https://crbug.com/676387#c84.

If you're wondering why there's a second wave of this, the first version of the
script handled "NON_EXPORTED_BASE(public base::NonThreadSafe)" but not
"public NON_EXPORTED_BASE(base::NonThreadSafe)"...

Note-worthy for the reviewer:
 * SequenceChecker enforces thread-safety but not thread-affinity!
   If the classes that were updated are thread-affine (use thread local
   storage or a third-party API that does) they should be migrated to
   ThreadChecker instead.
 * ~NonThreadSafe() used to implicitly check in its destructor
   ~Sequence/ThreadChecker() doesn't by design. To keep this CL a
   no-op, an explicit check was added to the destructor of migrated
   classes.
 * NonThreadSafe used to provide access to subclasses, as such
   the |sequence_checker_| member was made protected rather than
   private where necessary.

BUG=676387
This CL was uploaded by git cl split.

R=tommi@chromium.org
==========

to

==========
Replace deprecated base::NonThreadSafe in /content/browser/speech in favor of
SequenceChecker.

Note to crash team: This CL is a refactor and has no intended behavior change.

This change was scripted by https://crbug.com/676387#c84.

If you're wondering why there's a second wave of this, the first version of the
script handled "NON_EXPORTED_BASE(public base::NonThreadSafe)" but not
"public NON_EXPORTED_BASE(base::NonThreadSafe)"...

Note-worthy for the reviewer:
 * SequenceChecker enforces thread-safety but not thread-affinity!
   If the classes that were updated are thread-affine (use thread local
   storage or a third-party API that does) they should be migrated to
   ThreadChecker instead.
 * ~NonThreadSafe() used to implicitly check in its destructor
   ~Sequence/ThreadChecker() doesn't by design. To keep this CL a
   no-op, an explicit check was added to the destructor of migrated
   classes.
 * NonThreadSafe used to provide access to subclasses, as such
   the |sequence_checker_| member was made protected rather than
   private where necessary.

BUG=676387
This CL was uploaded by git cl split.

R=tommi@chromium.org

Review-Url: https://codereview.chromium.org/2919993002
Cr-Commit-Position: refs/heads/master@{#476748}
Committed:
https://chromium.googlesource.com/chromium/src/+/2510d3fbc38be38f5c8cd870dc9d...
==========

[commit-bot: I haz the power, 2017-06-02 19:20:32]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/2510d3fbc38be38f5c8cd870dc9d...