>From d4d41dbb38855188f8a1e398214ba0cffe90d5ea Mon Sep 17 00:00:00 2001 From: Bertram Felgenhauer Date: Tue, 10 Sep 2013 22:39:00 +0200 Subject: [PATCH] Clarify 'throwTo' documentation --- GHC/Conc/Sync.lhs | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/GHC/Conc/Sync.lhs b/GHC/Conc/Sync.lhs index 135c1fe..206eecc 100644 --- a/GHC/Conc/Sync.lhs +++ b/GHC/Conc/Sync.lhs @@ -328,11 +328,12 @@ killThread tid = throwTo tid ThreadKilled {- | 'throwTo' raises an arbitrary exception in the target thread (GHC only). +Exception delivery synchronizes between the source and target thread: 'throwTo' does not return until the exception has been raised in the -target thread. -The calling thread can thus be certain that the target -thread has received the exception. This is a useful property to know -when dealing with race conditions: eg. if there are two threads that +target thread. The calling thread can thus be certain that the target +thread has received the exception. Exception delivery is also atomic +with respect to other exceptions. Atomicity is a useful property to have +when dealing with race conditions: e.g. if there are two threads that can kill each other, it is guaranteed that only one of the threads will get to kill the other. -- 1.8.4.rc3