From: nalaginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 12033@debbugs.gnu.org
Subject: bug#12033: closed (Re: bug#12033: format should be faster)
Date: Thu, 23 Aug 2012 11:23:56 +0800 [thread overview]
Message-ID: <1345692236.5141.79.camel@Renee-SUSE.suse> (raw)
In-Reply-To: <87vcgcdoml.fsf@pobox.com>
hey guys! Any conclusion?
On Tue, 2012-08-21 at 21:35 +0200, Andy Wingo wrote:
> On Tue 21 Aug 2012 13:37, ludo@gnu.org (Ludovic Courtès) writes:
>
> >> It seems clear that in this case, Guile "should" know how to dispatch
> >> on the format string just once, outside of the loop, instead of doing
> >> it in every iteration.
> >
> > I think Andy would say: “inline cache!”. :-)
>
> :-)
>
> There are lots of possibilities here. You could "compile" a format
> string into a closure, and save it in a hash table. You could compile
> it to Scheme and then compile that procedure. You could recognize some
> common degenerate cases.
>
> Dunno! In this case I would compile the string into a closure. Seems
> pretty cheap and it would kill the dispatch overhead.
>
> Andy
next prev parent reply other threads:[~2012-08-23 3:23 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
2012-08-21 19:35 ` Andy Wingo
2012-08-23 3:23 ` nalaginrut [this message]
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=1345692236.5141.79.camel@Renee-SUSE.suse \
--to=nalaginrut@gmail.com \
--cc=12033@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).