3f87250a4f
This reverts commit 5f0eb93d2a44cec2102fc8c3757d5bb814bd145f. Reason for revert: Breaks downstream project. I'm going to fix that one and create a reland of this CL after. Original change's description: > Remove RTC_DISALLOW_COPY_AND_ASSIGN usages completely > > Bug: webrtc:13555, webrtc:13082 > Change-Id: Iff2cda6f516739419e97e975e03f77a98f74be03 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/249260 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Artem Titov <titovartem@webrtc.org> > Commit-Queue: (Daniel.L) Byoungchan Lee <daniel.l@hpcnt.com> > Cr-Commit-Position: refs/heads/main@{#35805} TBR=hta@webrtc.org,titovartem@webrtc.org,daniel.l@hpcnt.com,webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I33d497f1132adfe6d151023195a388d9b7d548f9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:13555, webrtc:13082 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/249364 Reviewed-by: Artem Titov <titovartem@webrtc.org> Owners-Override: Artem Titov <titovartem@webrtc.org> Reviewed-by: Andrey Logvin <landrey@webrtc.org> Reviewed-by: Björn Terelius <terelius@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35807}
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.