From: Ben Elliston <bje@wasabisystems.com>
To: cgen@sources.redhat.com
Subject: Re: fix for arm file generation, check in now, or later?
Date: Wed, 02 Jul 2003 00:50:00 -0000 [thread overview]
Message-ID: <87fzm62y2b.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <20030619191934.E160DB536@mail.sebabeach.org>
Doug Evans <dje@sebabeach.org> writes:
> The catch is that it exposes a slowness in the current
> implementation. It's one that eventually needs to be changed anyway
> and has always been anticipated: objects are recorded on lists so
> searching is slow.
This will go away if we switch to using Guile's object system, yes?
> I'm inclined to get this in and leave the speedup for another day.
I agree.
Ben
prev parent reply other threads:[~2003-07-02 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 19:16 Doug Evans
2003-07-02 0:50 ` Ben Elliston [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fzm62y2b.fsf@sashimi.wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=cgen@sources.redhat.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).