f22af3cca7
This reverts commit 18314bd8d2cb27fa58e4d304bbc428e3ed1736ba. Reason for revert: Breaks downstream test. Original change's description: > Distinguish between send and receive video codecs > > Even though send and receive codecs are the same, > they might have different support in HW. > Distinguish between send and receive codecs to be able to keep > track of which codecs have HW support. > > Bug: chromium:1029737 > Change-Id: I16a80da44c5061ca42f2aabda76e6bf0b879bf7b > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/161306 > Reviewed-by: Anders Carlsson <andersc@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Commit-Queue: Johannes Kron <kron@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#30041} TBR=steveanton@webrtc.org,andersc@webrtc.org,kron@webrtc.org Change-Id: I7e5807460006db613e9b3b369ec6036b88f164fd No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1029737 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/161662 Reviewed-by: Johannes Kron <kron@webrtc.org> Commit-Queue: Johannes Kron <kron@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30042}
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.