Commit 731d4021 by Abseil Team Committed by dinord

Fix typo: "a the condition" -> "a condition".

PiperOrigin-RevId: 443723710
Change-Id: Ic39b0cf2b289efa9cd9434616949dd08a1a35117
parent 7c6608d0
...@@ -2510,9 +2510,9 @@ void CondVar::Remove(PerThreadSynch *s) { ...@@ -2510,9 +2510,9 @@ void CondVar::Remove(PerThreadSynch *s) {
// before calling Mutex::UnlockSlow(), the Mutex code might be re-entered (via // before calling Mutex::UnlockSlow(), the Mutex code might be re-entered (via
// the logging code, or via a Condition function) and might potentially attempt // the logging code, or via a Condition function) and might potentially attempt
// to block this thread. That would be a problem if the thread were already on // to block this thread. That would be a problem if the thread were already on
// a the condition variable waiter queue. Thus, we use the waitp->cv_word // a condition variable waiter queue. Thus, we use the waitp->cv_word to tell
// to tell the unlock code to call CondVarEnqueue() to queue the thread on the // the unlock code to call CondVarEnqueue() to queue the thread on the condition
// condition variable queue just before the mutex is to be unlocked, and (most // variable queue just before the mutex is to be unlocked, and (most
// importantly) after any call to an external routine that might re-enter the // importantly) after any call to an external routine that might re-enter the
// mutex code. // mutex code.
static void CondVarEnqueue(SynchWaitParams *waitp) { static void CondVarEnqueue(SynchWaitParams *waitp) {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment