From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: or values bug?
Date: Mon, 05 Dec 2011 22:00:28 +0100 [thread overview]
Message-ID: <87wraapwcz.fsf@pobox.com> (raw)
In-Reply-To: <871usirb2s.fsf@pobox.com> (Andy Wingo's message of "Mon, 05 Dec 2011 21:57:15 +0100")
On Mon 05 Dec 2011 21:57, Andy Wingo <wingo@pobox.com> writes:
>> (let* ((vars (map (compose truncate lookup-var) gensyms))
>> ...)
>> ...)
>
> Better to truncate when adding variables to all expand-time
> environments, I would think, in the form of `(cut make-primcall #f
> 'values <>)'.
Rather, something like:
(define (truncate x)
(match x
((<const>) x)
;; similar provably singly-valued cases here
(else (make-primcall #f 'values (list x)))))
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-12-05 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 14:33 or values bug? rixed
2011-12-05 17:40 ` Ludovic Courtès
2011-12-05 20:57 ` Andy Wingo
2011-12-05 21:00 ` Andy Wingo [this message]
2011-12-06 17:57 ` Ludovic Courtès
2011-12-06 18:23 ` Andy Wingo
2011-12-06 6:51 ` rixed
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=87wraapwcz.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@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).