From: Andy Wingo <wingo@pobox.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: hygiene and macro-introduced toplevel bindings
Date: Fri, 01 Apr 2011 10:52:22 +0200 [thread overview]
Message-ID: <m3wrjeuzeh.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3oc5l8chm.fsf@unquote.localdomain> (Andy Wingo's message of "Tue, 08 Mar 2011 23:37:57 +0100")
Hello list,
On Tue 08 Mar 2011 23:37, Andy Wingo <wingo@pobox.com> writes:
> On Mon 28 Feb 2011 22:28, Andy Wingo <wingo@pobox.com> writes:
>
>> But you have to, I think. If that module that contained the above
>> define-syntactic-accessor expansion exports "foo", then in another
>> module you have:
>>
>> (define bar (lambda () (foo)))
>>
>> which expands to
>>
>> (define bar (lambda () val-234123))
>>
>> Val needs to be named.
>
> Everyone appears to want gensymmed names. OK! Let's consider this to
> be a bug, and that at some point in the future, Guile will start
> gensymming this names.
Just a reminder, the next step here is to implement gensyms with global
uniqueness. To do this we will use globally-unique gensyms. 128 bits
of randomness would be fine I think.
> If people want to make this go faster, start working on the gensyms.
If anyone is looking for a project, here is one.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-04-01 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 21:37 hygiene and macro-introduced toplevel bindings Andy Wingo
2011-02-27 22:02 ` Hans Aberg
2011-02-28 0:15 ` Andreas Rottmann
2011-02-28 21:28 ` Andy Wingo
2011-02-28 21:49 ` Noah Lavine
2011-03-08 22:33 ` Andy Wingo
2011-02-28 22:32 ` Ludovic Courtès
2011-03-08 22:37 ` Andy Wingo
2011-03-09 9:33 ` Hans Aberg
2011-03-09 20:14 ` Andy Wingo
2011-04-04 13:48 ` Hans Aberg
2011-04-01 8:52 ` 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=m3wrjeuzeh.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=a.rottmann@gmx.at \
--cc=guile-devel@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).