summaryrefslogtreecommitdiff
path: root/doc/ref/api-scheduling.texi
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2010-12-17 21:17:42 +0100
committerLudovic Courtès <ludo@gnu.org>2010-12-17 21:55:56 +0100
commit3e0e4f1d873c3fb3ab75ba42acdad822a1aad1a5 (patch)
tree45282c1c77c88203676ecf161792868a67af10b6 /doc/ref/api-scheduling.texi
parent863f11969d2da23406e3f38842e6b08a87452ef6 (diff)
downloadguile-3e0e4f1d873c3fb3ab75ba42acdad822a1aad1a5.tar.gz
Clarify doc regarding threading of `par-map' and `par-for-each'.
* doc/ref/api-scheduling.texi (Parallel Forms): Refine wording for `par-map' and `par-for-each'.
Diffstat (limited to 'doc/ref/api-scheduling.texi')
-rw-r--r--doc/ref/api-scheduling.texi3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/ref/api-scheduling.texi b/doc/ref/api-scheduling.texi
index a3bef7488..248d8b737 100644
--- a/doc/ref/api-scheduling.texi
+++ b/doc/ref/api-scheduling.texi
@@ -952,7 +952,8 @@ calls to complete.
The @var{proc} calls are @code{(@var{proc} @var{elem1} @dots{}
@var{elemN})}, where each @var{elem} is from the corresponding
@var{lst}. Each @var{lst} must be the same length. The calls are
-made in parallel, each in its own thread.
+potentially made in parallel, depending on the number of CPU cores
+available.
These functions are like @code{map} and @code{for-each} (@pxref{List
Mapping}), but make their @var{proc} calls in parallel.