838a5429ad
These indicate when a range-based for loop is using an index whose type (value, pointer, or reference) doesn't match what the loop actually extracts from the range. Fix by matching the actual type better. This shouldn't cause any behavior/performance change, just be slightly clearer about what's actually happening when reading the code. Bug: 1223264 Change-Id: Ibd208ce026bc59de8e39e6bf0cbd0d046a9da079 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2984967 Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Ted Choc <tedchoc@chromium.org> Reviewed-by: Ted Choc <tedchoc@chromium.org> Cr-Commit-Position: refs/heads/master@{#895821}
The optimization guide component contains code for processing hints and machine learning models received from the remote Chrome Optimization Guide Service.
Optimization Guide is a layered component (https://sites.google.com/a/chromium.org/dev/developers/design-documents/layered-components-design) to enable it to be easily used on all platforms.
Directory structure: core/: Shared code that does not depend on src/content/
- Contains the core functionalities to fetch and persist data received from the remote Chrome Optimization Guide Service, including but not limited to page load metadata and machine learning models. content/: Driver for the shared code based on the content layer
- Contains the functionality for interpreting the data received from the remote Chrome Optimization Guide Service.