From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: prior work on non-backtracking regex engine? Date: Sun, 07 Apr 2024 14:15:11 +0000 Message-ID: <87bk6lntsg.fsf@localhost> References: <3a9IKoS2YLqJYosdfpFVdq8ashG0LPPJdB-ugdUgJEqM6-O3RWFeCu01FUPYBsp87xchkX-z1PRlNqJQm8ge_h3v0ziCWcME2fx-6PW-UP4=@hypnicjerk.ai> <87il1qw9i9.fsf@localhost> <8eHWNAHASGpm2Qhs7mldB0VTdFaRW0NZJWi9ppNiCPZQ-QO8E7YLUXzJfT7LXYe1mTnwFGACouy7YroB8qsCFDbRuWYHr2gvOTagQY3TW7w=@hypnicjerk.ai> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7479"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "emacs-devel@gnu.org" To: Danny McClanahan , Mattias =?utf-8?Q?Engdeg=C3=A5?= =?utf-8?Q?rd?= , Eli Zaretskii , stefankangas@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 07 16:15:44 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rtTJA-0001iD-Et for ged-emacs-devel@m.gmane-mx.org; Sun, 07 Apr 2024 16:15:44 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rtTIQ-0005vm-8X; Sun, 07 Apr 2024 10:14:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rtTIN-0005un-9c for emacs-devel@gnu.org; Sun, 07 Apr 2024 10:14:55 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rtTIL-0000B7-It for emacs-devel@gnu.org; Sun, 07 Apr 2024 10:14:55 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 147B6240027 for ; Sun, 7 Apr 2024 16:14:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1712499292; bh=ofEMnL5/5SsvFMac/Hw8ig6kgGFtavcSU9QpKKiF0uo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=RzR066dHmhJZANWhtBt6zeHW8U5kFbmqgKpSIHGZNLMeHgsAqGPlGb+Ir2nsCQ/AC JS97wV2/Z5ZenZxomIOtkiR2rQuuTmB/0G0AREo29NwxYHH/NPKlEEXK2ijOvo5+dx IzVQZjAJkubZigiEFcIVIsbOVKaku7wgxA9SurKKKt5gNqurpbpl9bUOl2Qg2NTQvX n/KBaWL/IdRaxIhInXT+dIbQXijFpFE13FeLWKCFUhw+os0yD7Fak9Mmj4CHyJMPNu 7g0lBERaOx0buKqtOyNwBpALmwW4jpWbz0Pnaf3/wIri2Qikr+4gtcGdCwHAl9BaoQ XUg73roU0nkmQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VCDkf4rqgz9rxQ; Sun, 7 Apr 2024 16:14:50 +0200 (CEST) In-Reply-To: <8eHWNAHASGpm2Qhs7mldB0VTdFaRW0NZJWi9ppNiCPZQ-QO8E7YLUXzJfT7LXYe1mTnwFGACouy7YroB8qsCFDbRuWYHr2gvOTagQY3TW7w=@hypnicjerk.ai> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317589 Archived-At: Danny McClanahan 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 . Support Org development at , or support my work at