From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: mattiase@acm.org, larsi@gnus.org, 44861@debbugs.gnu.org,
shigeru.fukaya@gmail.com
Subject: bug#44861: 27.1; [PATCH] signal in `replace-regexp-in-string'
Date: Thu, 26 Nov 2020 16:41:32 +0200 [thread overview]
Message-ID: <83d000qixv.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=QEW4MPsQsTC1g61HuWSYFX6EFYLmZV01jX4HeZSCH9g@mail.gmail.com> (message from Stefan Kangas on Thu, 26 Nov 2020 05:43:29 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 26 Nov 2020 05:43:29 -0800
> Cc: 44861@debbugs.gnu.org, Shigeru Fukaya <shigeru.fukaya@gmail.com>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > But I wonder -- would it make sense to move the entire
> > replace-regexp-in-string function to C?
>
> Before we undertake any major changes in that direction, perhaps we
> should benchmark the relevant functions on the native-comp branch? It
> changes the benchmarks by quite a lot in some cases.
Benchmarking is always welcome, but I don't think we should dismiss
performance improvements by assuming everyone will use the
natively-compiled Lisp code VSN. I'm quite sure *.elc files will be
used in the observable future by many people. I also expect C code to
run faster than natively-compiled Lisp, when significant
implementation changes, such as those suggested by Mattias, are
involved.
prev parent reply other threads:[~2020-11-26 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 4:02 bug#44861: 27.1; [PATCH] signal in `replace-regexp-in-string' Shigeru Fukaya
2020-11-25 10:58 ` Mattias Engdegård
2020-11-25 14:58 ` Mattias Engdegård
2020-11-25 21:39 ` Stefan Kangas
2020-11-26 12:57 ` Mattias Engdegård
2020-11-26 13:12 ` Lars Ingebrigtsen
2020-11-26 13:39 ` Mattias Engdegård
2020-11-26 14:03 ` Lars Ingebrigtsen
2020-11-26 14:54 ` Mattias Engdegård
2020-11-29 13:28 ` Basil L. Contovounesios
2020-11-26 13:43 ` Stefan Kangas
2020-11-26 14:03 ` Lars Ingebrigtsen
2020-11-26 14:41 ` Eli Zaretskii [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=83d000qixv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44861@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=shigeru.fukaya@gmail.com \
--cc=stefankangas@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.
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.