From 5b343de44def5142086d99b7a0d885fd6ac01b53 Mon Sep 17 00:00:00 2001 From: Andy Wingo Date: Mon, 12 Dec 2016 21:29:19 +0100 Subject: Minor documentation tweak * fibers.texi (Barriers): Prefer the word "suspendable" over "rewindable". --- fibers.texi | 10 ++++++---- 1 file 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! -- cgit v1.3