| commit | 0f1d959599a4a08463a13f7f4bee183ab08aae45 | [log] [tgz] |
|---|---|---|
| author | Nigel Tao <nigeltao@chromium.org> | Fri Sep 22 04:45:21 2023 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 22 05:03:31 2023 |
| tree | 98a1ef7516015cbc781763fe96a72bdaea74a82e | |
| parent | e97c9a62b3b74f77f14c387912a11468d8b7e730 [diff] |
doc: add white background to raw_ptr_liveness.png Prior to this commit, that image (generated from raw_ptr_liveness.dot) had a transparent background. When viewing base/memory/raw_ptr.md rendered on source.chromium.org in "dark mode", the black-on-transparent diagram was unreadable. The regeneration and image-optimization was done by: $ dot -Tpng raw_ptr_liveness.dot -oout0.png $ convert out0.png -alpha remove out1.png $ pngcrush -brute -rem alla out1.png out2.png $ rm out0.png out1.png $ mv out2.png raw_ptr_liveness.png Before/after this commit: $ file raw_ptr_liveness.png raw_ptr_liveness.png: PNG image data, 1421 x 763, 8-bit gray+alpha, non-interlaced versus raw_ptr_liveness.png: PNG image data, 1421 x 763, 8-bit grayscale, non-interlaced Bug: None Change-Id: I3bccd3d0a511cafab1ee5a34c4948546fab18904 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4878353 Reviewed-by: Keishi Hattori <keishi@chromium.org> Auto-Submit: Nigel Tao <nigeltao@chromium.org> Reviewed-by: Kalvin Lee <kdlee@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1200046} NOKEYCHECK=True GitOrigin-RevId: c28faff7815d0dfe969599e105fb7f6107914d2f
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.