tmp/tmpqqd712d7/{from.md → to.md}
RENAMED
|
@@ -24,16 +24,12 @@ cond.notify_all();
|
|
| 24 |
|
| 25 |
*Synchronization:* The implied `lk.unlock()` call is sequenced after the
|
| 26 |
destruction of all objects with thread storage duration associated with
|
| 27 |
the current thread.
|
| 28 |
|
| 29 |
-
[*Note 1*: The supplied lock
|
| 30 |
-
|
| 31 |
-
lock ordering issues. After calling `notify_all_at_thread_exit` it is
|
| 32 |
-
recommended that the thread should be exited as soon as possible, and
|
| 33 |
-
that no blocking or time-consuming tasks are run on that
|
| 34 |
-
thread. — *end note*]
|
| 35 |
|
| 36 |
[*Note 2*: It is the user’s responsibility to ensure that waiting
|
| 37 |
threads do not erroneously assume that the thread has finished if they
|
| 38 |
experience spurious wakeups. This typically requires that the condition
|
| 39 |
being waited for is satisfied while holding the lock on `lk`, and that
|
|
|
|
| 24 |
|
| 25 |
*Synchronization:* The implied `lk.unlock()` call is sequenced after the
|
| 26 |
destruction of all objects with thread storage duration associated with
|
| 27 |
the current thread.
|
| 28 |
|
| 29 |
+
[*Note 1*: The supplied lock is held until the thread exits, which
|
| 30 |
+
might cause deadlock due to lock ordering issues. — *end note*]
|
|
|
|
|
|
|
|
|
|
|
|
|
| 31 |
|
| 32 |
[*Note 2*: It is the user’s responsibility to ensure that waiting
|
| 33 |
threads do not erroneously assume that the thread has finished if they
|
| 34 |
experience spurious wakeups. This typically requires that the condition
|
| 35 |
being waited for is satisfied while holding the lock on `lk`, and that
|