commit | 666cdd8a13c57f46db8b9c95aa36f1e19029ae79 | [log] [tgz] |
---|---|---|
author | Tom Cherry <tomcherry@google.com> | Tue Jul 14 21:21:06 2020 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Jul 14 21:21:06 2020 +0000 |
tree | 955e52eda3dade973ad5dac5a3f8425e1a0f2150 | |
parent | 0b15ffde25184a83f6e982ef6acd74c10f9fa2c5 [diff] | |
parent | 471eb55163ed2292258cda8673c2213159d861ed [diff] |
Run libbase_test as root and skip properties.too_long when not root am: aa8176185e am: 471eb55163 Original change: https://android-review.googlesource.com/c/platform/system/libbase/+/1360922 Change-Id: Ib42776502a47b88d8553990c0ef28d7514e08e1a
This library is a collection of convenience functions to make common tasks easier and less error-prone.
In this context, "error-prone" covers both "hard to do correctly" and "hard to do with good performance", but as a general purpose library, libbase's primary focus is on making it easier to do things easily and correctly when a compromise has to be made between "simplest API" on the one hand and "fastest implementation" on the other. Though obviously the ideal is to have both.
The intention is to cover the 80% use cases, not be all things to all users.
If you have a routine that's really useful in your project, congratulations. But that doesn't mean it should be here rather than just in your project.
The question for libbase is "should everyone be doing this?"/"does this make everyone's code cleaner/safer?". Historically we've considered the bar for inclusion to be "are there at least three unrelated projects that would be cleaned up by doing so".
If your routine is actually something from a future C++ standard (that isn't yet in libc++), or it's widely used in another library, that helps show that there's precedent. Being able to say "so-and-so has used this API for n years" is a good way to reduce concerns about API choices.
Unlike most Android code, code in libbase has to build for Mac and Windows too.
Code here is also expected to have good test coverage.
By its nature, it's difficult to change libbase API. It's often best to start using your routine just in your project, and let it "graduate" after you're certain that the API is solid.