tree 7daf20ef163320b8398561c5fabb50edbdcc2831
parent 8b117204c1db660563bf8da0531fcdc5c1f4dbe4
author Carlos Caballero <carlscab@google.com> 1552991200 +0000
committer Commit Bot <commit-bot@chromium.org> 1552991200 +0000

Store the current SequenceManagerImpl instance in TLS

Now that the backend for MessageLoop is always a SequenceManager it no
longer makes sense to have the TLS logic in MessageLoopCurrent.

Eventually MessageLoopBase will disappear completely and
MessageLoopCurrent will use the API exposed by SequenceManager. This
patch is a step in that direction.

Bug: 891670
Change-Id: I24a76ded54fcf4b95bc8192ce0fe413aaeee162d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497074
Commit-Queue: Carlos Caballero <carlscab@google.com>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641834}