
These spots used to compare base::ranges::search(...) against an .end() iterator. std::ranges::search() returns a subrange instead, so I was checking if it was empty; however, this isn't the same result if the input range is empty. Note that we generally cannot use std::ranges::includes() to express this, because it requires the input ranges be sorted. All these changes were introduced in the past week or so by me, during std::ranges conversions. Bug: 386918226 Change-Id: I1948fda67466d855ce1a7d81fe394949a20dc1b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6180717 Owners-Override: Lei Zhang <thestig@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1407561}
This directory contains UI frameworks used to build various user interface features. This directory is not intended to contain UI features (such as a keyboard).