0e1d3c5675
Many STL containers define these type aliases, and they are easier to work with than add_const_t<add_lvalue_reference_t<value_type>>. In a followup, `WTF::Vector` in Blink's conversion constructor from other containers will be SFINAE-guarded using these type aliases. Bug: chromium:1408442 Change-Id: I7790e6f462a32e7e49bc6468afeda6b2e6d4b631 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/300180 Reviewed-by: Tomas Gunnarsson <tommi@webrtc.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#39771}
How to write code in the api/ directory
Mostly, just follow the regular style guide, but:
- Note that
api/code is not exempt from the “.hand.ccfiles come in pairs” rule, so if you declare something inapi/path/to/foo.h, it should be defined inapi/path/to/foo.cc. - Headers in
api/should, if possible, not#includeheaders outsideapi/. It’s not always possible to avoid this, but be aware that it adds to a small mountain of technical debt that we’re trying to shrink. .ccfiles inapi/, on the other hand, are free to#includeheaders outsideapi/.
That is, the preferred way for api/ code to access non-api/ code is to call
it from a .cc file, so that users of our API headers won’t transitively
#include non-public headers.
For headers in api/ that need to refer to non-public types, forward
declarations are often a lesser evil than including non-public header files. The
usual rules still apply, though.
.cc files in api/ should preferably be kept reasonably small. If a
substantial implementation is needed, consider putting it with our non-public
code, and just call it from the api/ .cc file.