commit | e93e9b25656ed40d6a7f81bd3945362b4130c09e | [log] [tgz] |
---|---|---|
author | Hans Wennborg <hans@chromium.org> | Mon Jul 12 16:58:29 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 12 16:58:29 2021 |
tree | 52e9ef786e82379e28070eee6ead3b24e49b2315 | |
parent | 07917887620894f01f5db20e095c43a9487c2e6e [diff] |
Reland "[base] Don't include <ostream> in string_piece.h" This is a reland of 472bf833d128c8aa368ad70d3f64e12b45a559d7 Includes fix for fuchsia-x64-dbg in components/viz/service/surfaces/surface_reference.cc Original change's description: > [base] Don't include <ostream> in string_piece.h > > It's not needed, and adds ca 200 MB of compiler input to the build. > > This also adds an implementation of CHECK_OP's "argument stringification" > function for std::string values, since those previously relied on > operator<< for stringification which would now require including > <ostream> in many new files. > > Bug: 242216 > Change-Id: I34807204a82e622e50a5bbcabb7055c0b2f51f21 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3009579 > Commit-Queue: Hans Wennborg <hans@chromium.org> > Reviewed-by: danakj <danakj@chromium.org> > Owners-Override: danakj <danakj@chromium.org> > Cr-Commit-Position: refs/heads/master@{#900025} Cq-Include-Trybots: luci.chromium.try:fuchsia-compile-x64-dbg Bug: 242216 Change-Id: Ibdf16a1ec0307bd94aed2bfb327b7c64317e96bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3015330 Auto-Submit: Hans Wennborg <hans@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Owners-Override: danakj <danakj@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#900528}
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.