commit | ccc87ea3c625e43ab138e00ba2ef1a2d99756199 | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Thu Jun 15 13:17:45 2023 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 15 16:11:27 2023 |
tree | 17dffc8bc1d1c1e64819ae2c62fd554966f7a340 | |
parent | d0b8e8e4ee78a3bf5577f9b215e273098790f59f [diff] |
[Stats] Remove enum-like structs in favor of strings. Due to a limitation of RTCStatsMember<T> not supporting enums, as well as the fact that in JavaScript enums are represented as basic strings, the stats enums have always been represented by T=std::string. Now that we have WebIDL-ified[1] all RTCStats dictionaries and enum values are simply string-copied (example: [2]) it seems safe to assume that "stats enums are just strings" is here to stay. Therefore there is little value in having C++ structs that look like enums so I'm deleting those in favor of std::string operator==() comparisons, e.g. `if (rtp_stream.kind == "audio")`. This removes some lines of code from our code base. I mostly want to get rid of these because they were taking up about 20% of the rtcstats_objects.h real estate... [1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/peerconnection/rtc_stats_report.idl [2] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/peerconnection/rtc_stats_report.cc;l=667;drc=cf34e84c9df94256abfb1716ba075ed203975755 Bug: webrtc:15245 Change-Id: Iaf0827d7aecebc1cc02976a61663d5298d684f07 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/308680 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#40295}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.