From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: early termination for `map'
Date: Thu, 05 May 2011 23:12:29 +0200 [thread overview]
Message-ID: <m3zkn0vole.fsf@unquote.localdomain> (raw)
In-Reply-To: <87r58clwzc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 05 May 2011 22:21:27 +0200")
Hi,
On Thu 05 May 2011 22:21, ludo@gnu.org (Ludovic Courtès) writes:
> Yes, and I think we can keep rewriting SRFI-1 in Scheme, even in 2.0.
>
>> So I implemented map in Scheme
>
> Ooh, interesting. :-)
I pushed to stable-2.0. Let me know if you want me to back it out.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-05 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 15:24 early termination for `map' Andy Wingo
2011-05-05 15:56 ` Noah Lavine
2011-05-05 16:26 ` Ludovic Courtès
2011-05-05 18:40 ` Andy Wingo
2011-05-05 20:21 ` Ludovic Courtès
2011-05-05 21:12 ` Andy Wingo [this message]
2011-05-06 15:41 ` Ludovic Courtès
2011-05-08 15:05 ` ‘map’ and ‘for-each’ written in Scheme Ludovic Courtès
2011-05-08 15:31 ` Andy Wingo
2011-05-05 18:27 ` early termination for `map' Andy Wingo
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=m3zkn0vole.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).