commit | 54be7084e0861a0179a5fccd0b27edf7d7994bbb | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Wed Jan 17 09:32:23 2024 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 17 12:36:46 2024 |
tree | 8a576ef6b22112e1961b4c71ea81a972ab6c1082 | |
parent | b51c4b01f649fa24016670543eed2f87a6ac7705 [diff] |
[Stats] Attribute::ToString(), to replace member ValueToString/ToJson. Delete RTCStatsMember<T>::ValueToString() and ValueToJson() in favor of Attribute::ToString(). The difference between "ToString" and "ToJson" is that the "ToJson" version converts 64-bit integers and doubles to floating points with no more than ~15 digits of precision as to not exceed JSON's precision limitations. So only in edge cases of really large numbers or numbers with a silly number of digits will the two methods produce different results. Also JSON puts '\"' around map key names, e.g. "{\"foo\":123}" as opposed to "{foo:123}". Going forward we see no reason to maintain two different string converted paths that are this similar, so we only implement one Attribute::ToString() method which does what "ToJson" did. In the next CL we can delete RTCStatsMember<T>. Bug: webrtc:15164 Change-Id: Iaa8cf3bf14b40dc44664f75989832469603131c5 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/334640 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Evan Shrubsole <eshr@google.com> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41544}
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.