summaryrefslogtreecommitdiff
path: root/fibers.texi
diff options
context:
space:
mode:
Diffstat (limited to 'fibers.texi')
-rw-r--r--fibers.texi10
1 files changed, 6 insertions, 4 deletions
diff --git a/fibers.texi b/fibers.texi
index c0744ff..5eb168c 100644
--- a/fibers.texi
+++ b/fibers.texi
@@ -791,14 +791,16 @@ currently. If you need to yield to the scheduler, then at least do a
When a fiber suspends, Fibers uses @code{abort-to-prompt} to save the
fiber's continuation, saving each pending computation in that fiber to
the heap. When the fiber resumes, Fibers invokes the saved
-continuation, effectively rewinding these saved stack frames back onto
+continuation, effectively replaying these saved stack frames back onto
the current stack. For this operation to succeed, the saved
-continuation needs to be @var{rewindable}.
+continuation needs to be @dfn{suspendable}. A suspendable
+continuation should be able to be resumed after the call to
+@code{abort-to-prompt}.
-Most continuations in Guile are rewindable. However, not all of them
+Most continuations in Guile are suspendable. However, not all of them
are. It's possible to explicitly instate a continuation barrier
(@pxref{Continuation Barriers,,,guile.info,Guile Reference Manual})
-that will prevent rewinding the continuation:
+that will allow the continuation to be aborted but not reinstated:
@example
;; If put-message suspends, we will never resume!