Use backticks not vertical bars to denote variables in comments for /rtc_base
Bug: webrtc:12338 Change-Id: I72fcb505a92f03b2ace7160ee33d555a977eddfd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/226955 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34587}
This commit is contained in:
committed by
WebRTC LUCI CQ
parent
22a6b2dcad
commit
96e3b991da
@ -78,8 +78,8 @@ class OperationTracker {
|
||||
callback();
|
||||
}
|
||||
|
||||
// This operation is completed asynchronously; it pings |background_thread_|,
|
||||
// blocking that thread until |unblock_operation_event| is signaled and then
|
||||
// This operation is completed asynchronously; it pings `background_thread_`,
|
||||
// blocking that thread until `unblock_operation_event` is signaled and then
|
||||
// completes upon posting back to the thread that the operation started on.
|
||||
// Note that this requires the starting thread to be executing tasks (handle
|
||||
// messages), i.e. must not be blocked.
|
||||
@ -191,7 +191,7 @@ class OperationTrackerProxy {
|
||||
return operation_complete_event;
|
||||
}
|
||||
|
||||
// The order of completed events. Touches the |operation_tracker_| on the
|
||||
// The order of completed events. Touches the `operation_tracker_` on the
|
||||
// calling thread, this is only thread safe if all chained operations have
|
||||
// completed.
|
||||
const std::vector<Event*>& completed_operation_events() const {
|
||||
@ -212,7 +212,7 @@ class SignalOnDestruction final {
|
||||
RTC_DCHECK(destructor_called_);
|
||||
}
|
||||
~SignalOnDestruction() {
|
||||
// Moved objects will have |destructor_called_| set to null. Destroying a
|
||||
// Moved objects will have `destructor_called_` set to null. Destroying a
|
||||
// moved SignalOnDestruction should not signal.
|
||||
if (destructor_called_) {
|
||||
*destructor_called_ = true;
|
||||
|
||||
Reference in New Issue
Block a user