Deprecate NonThreadSafe in components/data_reduction_proxy in favor of SequenceChecker.

Deprecate NonThreadSafe in components/data_reduction_proxy 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#c8.

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 implcitly 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=bolian@chromium.org

Review-Url: https://codereview.chromium.org/2909973002
Cr-Commit-Position: refs/heads/master@{#475598}
Committed: https://chromium.googlesource.com/chromium/src/+/e9f5b26537f6e4a7fb7552c96cb23b04d9d7db7b

[gab, 2017-05-29 19:20:50]

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

[gab, 2017-05-29 19:20:52]

Hi, this is an automated change made by https://crbug.com/676387#c8 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.

If it didn't pass CQ dry-run it may be a simple patch failure or an IWYU failure
from having this being a partial CL... please review anyways and a human will
look at the failure (and ping for re-review if anything major is required..). It
is known to compile all targets on Windows at r474679...  manual tweaks will
likely be required to smoothen things off, bear with me!

Thanks!
Gab

[commit-bot: I haz the power, 2017-05-29 19:21:05]

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

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

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

Dry run: This issue passed the CQ dry run.

[gab, 2017-05-30 01:26:04]

Description was changed from

==========
Deprecate NonThreadSafe in components/data_reduction_proxy in favor of
SequenceChecker.

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

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 implcitly 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=bolian@chromium.org
==========

to

==========
Deprecate NonThreadSafe in components/data_reduction_proxy 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#c8.

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 implcitly 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=bolian@chromium.org
==========

[tbansal1, 2017-05-30 18:06:29]

tbansal@chromium.org changed reviewers:
+ tbansal@chromium.org

[tbansal1, 2017-05-30 18:06:29]

The CQ bit was checked by tbansal@chromium.org

[tbansal1, 2017-05-30 18:06:30]

lgtm

[commit-bot: I haz the power, 2017-05-30 18:07:13]

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-30 18:11:53]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1496167589818970, "parent_rev":
"dc9a99aeb236d40290aa81dab893740688c1ce2a", "commit_rev":
"e9f5b26537f6e4a7fb7552c96cb23b04d9d7db7b"}

[commit-bot: I haz the power, 2017-05-30 18:12:01]

Description was changed from

==========
Deprecate NonThreadSafe in components/data_reduction_proxy 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#c8.

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 implcitly 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=bolian@chromium.org
==========

to

==========
Deprecate NonThreadSafe in components/data_reduction_proxy 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#c8.

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 implcitly 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=bolian@chromium.org

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

[commit-bot: I haz the power, 2017-05-30 18:12:02]

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