GitLab

It was always called directly from ModelAssociationManager::Associate().
The only non-trivial thing Associate() did was make sure it gets called
only once per datatype and ModelAssociationManager::Initialize().
DataTypeManagerImpl now takes care of that itself, by storing a map of
ConfigurationStats instead of a vector.
One small behavior difference is that the ordering of those
ConfigurationStats is not the same anymore. AFAICT, nothing depends on
the ordering, and anyway each ConfigurationStats entry contains
ordering information in the form of "types_configured_before", so this
should not matter.

Bug: 1102837
Change-Id: I95d71e8fa98b8b382bc182dc11e1fcbd6e58c4f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2490109Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820192}