89e130a2d0
This is a reland of d6bb18479f4d9e258ae3e05427c101fb9e635373 Chromium problem fixed in https://webrtc-review.googlesource.com/c/src/+/153485 Original change's description: > Delete methods EncodedImage::Allocate and EncodedImageBufferInterface::Realloc > > Bug: webrtc:9378 > Change-Id: I3b03656769623647fcbb4f9125a3e920b7650fe9 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/155961 > Reviewed-by: Philip Eliasson <philipel@webrtc.org> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Commit-Queue: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#29458} Bug: webrtc:9378 Change-Id: I062262e87e115666ed4c92985ca75328e8d0c65f Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/157441 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Commit-Queue: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29537}
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.