5ab79e62f6
This is a reland of 16d4c4d4fbb8644033def1091d2d5c941c1b01fa after downstream project was updated to be prepared for the new SdpType. Original change's description: > Implement rollback for setRemoteDescription > > Bug: chromium:980875 > Change-Id: I4575e9ad1902a20937f9812f49edee2a2441f76d > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/153525 > Commit-Queue: Eldar Rello <elrello@microsoft.com> > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#29422} TBR=steveanton@webrtc.org Bug: chromium:980875 Change-Id: Iba8d25bf2dc481b25a03eeae9818bd5f4c3eaa2d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/156569 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29460}
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.