commit | af1e407bfc9566e2d06f4a7792cdb27390868db0 | [log] [tgz] |
---|---|---|
author | Kalvin Lee <kdlee@chromium.org> | Thu Jun 30 02:12:05 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 30 02:37:27 2022 |
tree | 70ea45cd22eaba4e7534c8f6ab027431ffa4f068 | |
parent | cdfaa8c90356c8ac0fe4177c333b2ef8ad50a6a3 [diff] |
[PA] Namespace migration (40 of N) This change erases multiple `base::` aliases from PartitionAlloc headers. Bug: 1288247 Change-Id: I7eb4b10e251521aaae52528b3b09db0d49cdd4c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3722838 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Bartek Nowierski <bartekn@chromium.org> Commit-Queue: Kalvin Lee <kdlee@chromium.org> Reviewed-by: Anton Bikineev <bikineev@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/main@{#1019419} NOKEYCHECK=True GitOrigin-RevId: 9833bf903aed41264ba97975641cdd8b7f2d1ae0
Contains a written down set of principles and other information on //base. Please add to it!
Chromium is a very mature project. Most things that are generally useful are already here and things not here aren't generally useful.
The bar for adding stuff to base is that it must have demonstrated wide applicability. Prefer to add things closer to where they're used (i.e. “not base”), and pull into base only when needed. In a project our size, sometimes even duplication is OK and inevitable.
Adding a new logging macro DPVELOG_NE
is not more clear than just writing the stuff you want to log in a regular logging statement, even if it makes your calling code longer. Just add it to your own code.
If the code in question does not need to be used inside base, but will have multiple consumers across the codebase, consider placing it in a new directory under components/ instead.
base is written for the Chromium project and is not intended to be used outside it. Using base outside of src.git is explicitly not supported, and base makes no guarantees about API (or even ABI) stability (like all other code in Chromium). New code that depends on base/ must be in src.git. Code that's not in src.git but pulled in through DEPS (for example, v8) cannot use base.
Owners are added when a contributor has shown the above qualifications and when they express interest. There isn't an upper bound on the number of OWNERS.
Since the primitives provided by //base are used very widely, it is important to ensure they scale to the necessary workloads and perform well under all supported platforms. The base_perftests
target is a suite of synthetic microbenchmarks that measure performance in various scenarios:
Regressions in these benchmarks can generally by caused by 1) operating system changes, 2) compiler version or flag changes or 3) changes in //base code itself.