From: Ihor Radchenko <yantar92@posteo.net>
To: "Danny McClanahan" <dmcc2@hypnicjerk.ai>,
"Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>,
stefankangas@gmail.com
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: prior work on non-backtracking regex engine?
Date: Sun, 07 Apr 2024 14:15:11 +0000 [thread overview]
Message-ID: <87bk6lntsg.fsf@localhost> (raw)
In-Reply-To: <8eHWNAHASGpm2Qhs7mldB0VTdFaRW0NZJWi9ppNiCPZQ-QO8E7YLUXzJfT7LXYe1mTnwFGACouy7YroB8qsCFDbRuWYHr2gvOTagQY3TW7w=@hypnicjerk.ai>
Danny McClanahan <dmcc2@hypnicjerk.ai> writes:
>> P.S. Better regexp engine would be very welcome.
>
> ... So in my amateur evaluation, emacs actually seems very well-placed to take advantage of high-performance regex engine techniques without any big structural changes.
> ...
> I would *really like* to eventually have emacs depend on an existing
> regex engine like re2 or rust regex to take advantage of their
> bugfixes and optimizations...
> ...
> Informal sketch of work outline: ...
Please, be aware that I have little to do with Emacs regexp maintenance.
CCing the actual maintainers.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-04-07 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 15:41 prior work on non-backtracking regex engine? Danny McClanahan
2024-03-12 23:45 ` Danny McClanahan
2024-03-13 13:23 ` Ihor Radchenko
2024-04-07 4:42 ` Danny McClanahan
2024-04-07 14:15 ` Ihor Radchenko [this message]
2024-04-08 12:19 ` Helmut Eller
2024-04-08 13:13 ` Eli Zaretskii
2024-04-08 14:00 ` Po Lu
2024-04-08 14:23 ` Eli Zaretskii
2024-04-12 0:12 ` Danny McClanahan
2024-04-17 14:23 ` Clément Pit-Claudel
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk6lntsg.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dmcc2@hypnicjerk.ai \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).