From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Andy Wingo <INVALID.NOREPLY@gnu.org>
Cc: Szavai Gyula <szgyg@ludens.elte.hu>, bug-guile@gnu.org
Subject: Re: [bug #30070] multiple returns from map
Date: Sat, 13 Aug 2011 17:56:53 +0200 [thread overview]
Message-ID: <CAGua6m3ypMFj6nf73WVGBpFpH0kb4HznMoHvKDxzHMkP9OYtPw@mail.gmail.com> (raw)
In-Reply-To: <20110812-210321.sv20118.97813@savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Yes a tail pointer was a mind slip . But I did
changed the final reverse! to the functional reverse in the srfi-1 version
of map
and doing that should be enough. You pay at most 2x time wise due to the
need to
allocate twice as many conses, But there is no need to introduce new stack
features
as far as I can see.
/Stefan
On Fri, Aug 12, 2011 at 11:03 PM, Andy Wingo <INVALID.NOREPLY@gnu.org>wrote:
> Follow-up Comment #2, bug #30070 (project guile):
>
> Stefan, the tail pointer does preserve performance, but it does not
> preserve
> the R6RS invariant about multiple returns.
>
> Szavai is right. Perhaps we should provide some other definition of `map'
> within R6RS to satisfy this requirement. However, a proper solution looks
> more like recursion than iteration, and to do that with arbitrary-sized
> lists
> will require Guile to implement extendable stacks, which is a significant
> hack.
>
> _______________________________________________________
>
> Reply to this item at:
>
> <http://savannah.gnu.org/bugs/?30070>
>
> _______________________________________________
> Message sent via/by Savannah
> http://savannah.gnu.org/
>
>
[-- Attachment #2: Type: text/html, Size: 1643 bytes --]
next prev parent reply other threads:[~2011-08-13 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 18:23 [bug #30070] multiple returns from map Szavai Gyula
2011-07-15 10:45 ` Stefan Israelsson Tampe
2011-08-12 21:03 ` Andy Wingo
2011-08-13 15:56 ` Stefan Israelsson Tampe [this message]
2011-08-14 20:03 ` Andy Wingo
2011-08-14 20:52 ` Stefan Israelsson Tampe
2011-08-17 21:29 ` 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=CAGua6m3ypMFj6nf73WVGBpFpH0kb4HznMoHvKDxzHMkP9OYtPw@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=INVALID.NOREPLY@gnu.org \
--cc=bug-guile@gnu.org \
--cc=szgyg@ludens.elte.hu \
/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).