From: Mark H Weaver <mhw@netris.org>
To: guile-devel@gnu.org
Subject: Re: (set! (@@ MOD NAME) EXP) considered harmful
Date: Wed, 2 Sep 2009 12:25:05 -0400 [thread overview]
Message-ID: <20090902162505.GA3339@fibril.netris.org> (raw)
In-Reply-To: <877hwhqq2g.fsf@netris.org>
Sorry, I meant to say that (set! (@ MOD NAME) EXP) should be
considered harmful as well.
Mark
On Wed, Sep 02, 2009 at 12:17:11PM -0400, Mark H Weaver wrote:
> The ability to set! arbitrary module top-level variables from outside
> the module, using the syntax (set! (@@ MOD NAME) EXP), destroys our
> ability to several important optimizations.
>
> As long as such ability exists, we must pessimistically assume that
> any module top-level variable might change at any time, which means,
> for example, that we cannot inline top-level procedure applications
> from within the module itself. This could be a HUGE efficiency win in
> the common case where such top-level procedures are never set! from
> within the module.
>
> Now that we have proper hygienic macros, is this functionality still
> required? If we're going to remove it, pre-2.0 seems like a good time
> to do so. We won't get another opportunity for several years.
>
> Mark
>
next prev parent reply other threads:[~2009-09-02 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 16:17 (set! (@@ MOD NAME) EXP) considered harmful Mark H Weaver
2009-09-02 16:25 ` Mark H Weaver [this message]
2009-09-03 14:57 ` Andy Wingo
2009-09-15 21:23 ` Neil Jerram
2009-09-17 22:16 ` Ludovic Courtès
2009-09-18 14:29 ` Andy Wingo
2009-09-18 20:40 ` Neil Jerram
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=20090902162505.GA3339@fibril.netris.org \
--to=mhw@netris.org \
--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).