2a96ab20b2
Calls to the time functions in Clock can have side effects in some circumstances. It's also questionable if it's a good idea to allow repeated calls to a const method return different values without any changed to the class instance. Bug: webrtc:10270 Change-Id: I316f9788adac954c52b0f9230881b872c54a7ac9 Reviewed-on: https://webrtc-review.googlesource.com/c/120348 Commit-Queue: Sebastian Jansson <srte@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26482} |
||
|---|---|---|
| .. | ||
| clock_unittest.cc | ||
| clock.cc | ||
| cpu_features_android.c | ||
| cpu_features_linux.c | ||
| cpu_features.cc | ||
| cpu_info.cc | ||
| event.cc | ||
| field_trial.cc | ||
| metrics_default_unittest.cc | ||
| metrics_unittest.cc | ||
| metrics.cc | ||
| ntp_time_unittest.cc | ||
| rtp_to_ntp_estimator_unittest.cc | ||
| rtp_to_ntp_estimator.cc | ||
| sleep.cc | ||