From: Zefram <zefram@fysh.org>
To: 21897@debbugs.gnu.org
Subject: bug#21897: escape continuation passes barrier
Date: Fri, 13 Nov 2015 03:31:26 +0000 [thread overview]
Message-ID: <20151113033126.GA16544@fysh.org> (raw)
scheme@(guile-user)> (use-modules (ice-9 control))
scheme@(guile-user)> (call/ec (lambda (c) (with-continuation-barrier (lambda () (c "through continuation"))) "c-w-b returned"))
$1 = "through continuation"
The continuation barrier works fine on call/cc continuations and
on throw/catch, but doesn't block call/ec continuations. The manual
doesn't mention any difference in behaviour for this case, nor can I
see any obvious justification for it. The manual's statement that
# Thus, `with-continuation-barrier' returns exactly once.
is false in this case. I think a continuation barrier should block the
use of the call/ec continuation.
-zefram
next reply other threads:[~2015-11-13 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 3:31 Zefram [this message]
2016-06-24 16:23 ` bug#21897: escape continuation passes barrier Andy Wingo
2020-03-29 17:28 ` bug#21897: verified in 3.0.2 Matt Wette
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151113033126.GA16544@fysh.org \
--to=zefram@fysh.org \
--cc=21897@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).