unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Zefram <zefram@fysh.org>
Cc: 21900-done@debbugs.gnu.org
Subject: bug#21900: map is not continuation-safe
Date: Mon, 20 Jun 2016 18:01:35 +0200	[thread overview]
Message-ID: <87twgng880.fsf@pobox.com> (raw)
In-Reply-To: <20151113083421.GK13455@fysh.org> (zefram@fysh.org's message of "Fri, 13 Nov 2015 08:34:21 +0000")

On Fri 13 Nov 2015 09:34, Zefram <zefram@fysh.org> writes:

> With Guile 2.0.11:
>
> scheme@(guile-user)> (define cc #f)
> scheme@(guile-user)> (map (lambda (v) (if (= v 0) (call/cc (lambda (c) (set! cc c) 0)) (+ v 1))) '(10 20 30 0 40 50 60))
> $1 = (11 21 31 0 41 51 61)
> scheme@(guile-user)> (cc 5)
> $2 = (61 51 41 0 31 5 41 51 61)
>
> It worked correctly in Guile 1.8.

"Fixed" in the upcoming 2.2 release, though I think we consider this
more of an implementation detail than a bug.

Andy





      reply	other threads:[~2016-06-20 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  8:34 bug#21900: map is not continuation-safe Zefram
2016-06-20 16:01 ` Andy Wingo [this message]

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=87twgng880.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=21900-done@debbugs.gnu.org \
    --cc=zefram@fysh.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).