all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: 75359@debbugs.gnu.org, acorallo@gnu.org
Subject: bug#75359: [scratch/elisp-benchmarks] test dependencies
Date: Mon, 06 Jan 2025 09:59:19 -0500	[thread overview]
Message-ID: <jwvv7usngg3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878qrohucz.fsf@protonmail.com> (Pip Cet's message of "Mon, 06 Jan 2025 14:47:44 +0000")

> Context: I have extended ERT so it has some minimal benchmarking
> functionality, after investigating (twice) whether elisp-benchmarks.el
> can't be made to do the job.  My conclusion was that that would take too
> much time, we should use ERT and ditch elisp-benchmarks.el, modifying
> the benchmarks instead.

I don't have any opinion on that.  The `elisp-benchmark.el` code itself
is very small/trivial, so rewriting it should be quite easy.

[ Then again, I can't think of any reason why any of it would take "much
  time", whether modifying `elisp-benchmarks.el`, or extending ERT, or
  writing it all from scratch.  So I'm probably missing something.  ]


        Stefan






      reply	other threads:[~2025-01-06 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04 16:37 bug#75359: [scratch/elisp-benchmarks] test dependencies Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-06  9:53 ` Andrea Corallo
2025-01-06 14:35   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-06 14:47     ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-06 14:59       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=jwvv7usngg3.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=75359@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pipcet@protonmail.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.