unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: 12033@debbugs.gnu.org, nalaginrut <nalaginrut@gmail.com>
Subject: bug#12033: closed (Re: bug#12033: format should be faster)
Date: Tue, 21 Aug 2012 15:40:42 +0200	[thread overview]
Message-ID: <87obm4pdlx.fsf@gnu.org> (raw)
In-Reply-To: <CA+U71=ObOYcqrLAWjoodRC-fmh3rFC_MJpiiiOK6HdkUF1zngA@mail.gmail.com> (Noah Lavine's message of "Tue, 21 Aug 2012 07:52:39 -0400")

Hi,

Noah Lavine <noah.b.lavine@gmail.com> skribis:

> What I was hoping to do is have a macro that is also
> identifier-syntax, so if format is used in a way that can't be
> macroexpanded, it falls back to the procedure. I think I've seen an
> example of this before, but I'm not sure where.

Yes, ‘define-inlinable’ does that, for instance.

[...]

> However, I wonder if the partial evaluator would actually solve this
> problem if it knew how to do cross-module inlining. That's another big
> project, but it could be a way to solve this problem and keep format
> as a function.

If ‘format’ were defined with ‘define-inlinable’ (which it cannot
currently, because rest arguments aren’t supported–which should be
fixed), then peval could specialize the ‘format’ code at the call site.
I wonder how far it’d go, though.

Ludo’.





  reply	other threads:[~2012-08-21 13:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  6:11 bug#12033: format should be faster nalaginrut
2012-08-18 22:19 ` Ludovic Courtès
2012-08-20  6:27   ` nalaginrut
2012-08-20 21:51     ` Ludovic Courtès
     [not found] ` <handler.12033.D12033.134549952018901.notifdone@debbugs.gnu.org>
2012-08-20 22:37   ` bug#12033: closed (Re: bug#12033: format should be faster) Ludovic Courtès
2012-08-21  2:50     ` nalaginrut
2012-08-21  3:00       ` Noah Lavine
2012-08-21  3:32         ` Ian Price
2012-08-21 11:37         ` Ludovic Courtès
2012-08-21 11:52           ` Noah Lavine
2012-08-21 13:40             ` Ludovic Courtès [this message]
2012-08-21 19:35           ` Andy Wingo
2012-08-23  3:23             ` nalaginrut
2012-08-23 21:55               ` Ludovic Courtès

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=87obm4pdlx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=12033@debbugs.gnu.org \
    --cc=nalaginrut@gmail.com \
    --cc=noah.b.lavine@gmail.com \
    /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).