From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: (set! (@@ MOD NAME) EXP) considered harmful
Date: Fri, 18 Sep 2009 16:29:59 +0200 [thread overview]
Message-ID: <m3pr9o9vh3.fsf@pobox.com> (raw)
In-Reply-To: <871vm52p4o.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 18 Sep 2009 00:16:39 +0200")
On Fri 18 Sep 2009 00:16, ludo@gnu.org (Ludovic Courtès) writes:
> Perhaps the compiler should make it possible to choose a tradeoff
> between dynamicity and performance, e.g., by actually honoring the ‘:O’
> compile option?
Sure, sounds good to me. We should also have in-source directives, like
(declare (speed 3)) or such.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-09-18 14:29 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
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 [this message]
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=m3pr9o9vh3.fsf@pobox.com \
--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).