commit | 6f013586f37900aef253908c7c66a17bd66d1d4e | [log] [tgz] |
---|---|---|
author | Peter Kasting <pkasting@chromium.org> | Thu Nov 07 22:19:26 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 07 22:19:26 2024 |
tree | 1c35dded1b53afe4fc2acd5ec4329aa391693333 | |
parent | 9ddc1624637c8cfa8ef50a95abd779e0ba4d67f6 [diff] |
Span API tweaks, part 3. * Adjust construction/conversion constraints to be slightly more correct (e.g. properly prevent make_span() from accepting things CTAD won't, such as non-const non-borrowed non-legacy rvalue ranges) and match std::span better. Added some nocompile tests. * Prevent the legacy range constructor from accepting ranges that are actually "modern" ranges but fail that constructor's constraints (e.g. std::array or non-borrowed ranges of non-const T). (This is a stepping stone towards removing this constructor entirely, so we don't "backslide" on supposedly-disallowed usage, like construction of writable spans from non-const, non-borrowed ranges; added nocompile tests to verify.) * Tweak deduction guides to match std::span better (though not yet perfectly). (This is a stepping stone toward adding the std::initializer_list constructor.) Bug: 364987728 Change-Id: Ie8449a901b41ded48906a409c5fd5c0ffee9ca35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5985655 Auto-Submit: Peter Kasting <pkasting@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1379978}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.