| commit | 537c80cb86054dd142a212570ba682796a1e6e80 | [log] [tgz] |
|---|---|---|
| author | Joe Mason <joenotcharles@google.com> | Sun Oct 19 02:11:42 2025 |
| committer | Copybara-Service <copybara-worker@google.com> | Sun Oct 19 02:18:43 2025 |
| tree | cd86add019c45d402b19cc6e852414dfffce33e8 | |
| parent | be83ab5e9402ef2f8aeae451552784c9811f4f0a [diff] |
Split ByteCount into ByteSize and ByteSizeDelta The constructor functions KiB, etc. are split into unsigned KiBU (returns ByteSize) and signed KiBS (returns ByteSizeDelta), with a TODO to migrate existing uses of KiB, etc. to the unsigned variants and then rename KiBU to KiB. Bug: 448661443 Change-Id: I48a74e30e960722e0f52701a5237a815a12f2328 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7042842 Commit-Queue: Joe Mason <joenotcharles@google.com> Reviewed-by: Francois Pierre Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/main@{#1531902} NOKEYCHECK=True GitOrigin-RevId: f75632db8275e73d793060a3bffcbe24b5700081
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:
thread_local, the implementation in //base, the POSIX/WinAPI directly)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.