From: Greg Troxel <gdt@ir.bbn.com>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-user@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: "Pace is nothing without guile"
Date: Sun, 13 Jul 2008 14:24:18 -0400 [thread overview]
Message-ID: <rmilk05hcbx.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <49dd78620807131006m4efc2a96v2d9778b6c4a501b4@mail.gmail.com> (Neil Jerram's message of "Sun, 13 Jul 2008 18:06:17 +0100")
My immediate reaction is that test suites aren't good benchmarks because
we will often want to add to test suites, while changing the benchmark
invalidates previous data so we will not want to change the benchmark.
Now, if you mean to use the test suite as a collection of
micro-benchmarks, so that we just have a rule that individual tests
aren't modified without serious cause, but new ones can be added, then
that makes senes.
next prev parent reply other threads:[~2008-07-13 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 17:06 "Pace is nothing without guile" Neil Jerram
2008-07-13 18:24 ` Greg Troxel [this message]
2008-07-13 22:31 ` Neil Jerram
2008-07-15 19:21 ` 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=rmilk05hcbx.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=neiljerram@googlemail.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).