unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny McClanahan <dmcc2@hypnicjerk.ai>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Augusto Stoffel <arstoffel@gmail.com>,
	Helmut Eller <eller.helmut@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Danny McClanahan <dmcc2@hypnicjerk.ai>,
	pipcet@protonmail.com, emacs-devel@gnu.org, mattiase@acm.org,
	acorallo@gnu.org, stefankangas@gmail.com
Subject: Re: [PATCH] add compiled regexp primitive lisp object
Date: Tue, 26 Nov 2024 18:50:36 +0000	[thread overview]
Message-ID: <231nVA_JeeFRqN-Jr2qUlIPAwaTNYT2G1qiiSY5Y4hRBFChCiK0sgenqrHcARaGyopcDt5XzTfk63BzPZAs0-8syQ-UDWVqoOz2B3mYrvuY=@hypnicjerk.ai> (raw)
In-Reply-To: <bI8s6V5mGnaISfUxrwgTc7xomnZKNE3_7NdhdFVxGZ5wqc1EBVenxQKFBSik0vDuqeMvq2LZ1cgwf0bmcp1t0K__9QIvf1MvmzD-R0w5k6c=@hypnicjerk.ai>

The talk description I submitted a bit ago can be viewed at https://emacsconf.org/2024/talks/regex/ for anyone who is interested. I am planning to be around over IRC for a good amount of the conference but especially around the talk time.

The description serves partially as a manifesto for my own purposes, and also as a self study of how Emacs allows the user to extract so much meaning out of pattern matching, as part of a general conception of Emacs as a mode of technical empowerment.

On Tuesday, November 26th, 2024 at 13:05, Danny McClanahan <dmcc2@hypnicjerk.ai> wrote:

> 
> 
> Thanks so much for this thorough and thoughtful response! I am compiling a 20-minute recorded talk for the upcoming EmacsConf regarding these discussions and investigations. I am also now waiting for a response from graduate school, during which I hope to then have more time to pin down several of the threads raised by this discussion.
> 
> This has all been immensely helpful and I really appreciate how responsive emacs-devel has been in elaborating much of the packed-together assumptions I was making.
> 
> On Tuesday, August 13th, 2024 at 21:32, Stefan Monnier monnier@iro.umontreal.ca wrote:
> 
> > > Ignoring the issue that regexps may be syntax-table dependent and other
> > 
> > > complications (issues which also would need to be addressed in the
> > > proposed approach), what would be the advantage of exposing compiled
> > > regexp objects versus having an infinite regexp cache?
> > 
> > I can think of the following:
> > 
> > - Not having to pay as much attention to the engineering of the cache
> > (it's currently small because the lookup could become costly, with
> > the current implementation).
> > 
> > - We could offer to spend a fair bit more time optimizing the compiled
> > code (e.g. removing backtracking).
> > 
> > But there's always the question of whether it's worth the complexity.
> > IOW, what are the concrete use cases where it makes
> > a measurable difference.
> > 
> > Stefan
> 
> 
>



  reply	other threads:[~2024-11-26 18:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  5:08 [PATCH] add compiled regexp primitive lisp object Danny McClanahan
2024-07-30 13:02 ` Philip Kaludercic
2024-07-31 22:33   ` dmcc2
2024-08-01  1:04 ` Pip Cet
2024-08-04 23:38   ` Danny McClanahan
2024-08-05  3:47     ` dmcc2
2024-08-05  4:39   ` Danny McClanahan
2024-08-05  7:15     ` Danny McClanahan
2024-08-05 17:55     ` Pip Cet
2024-08-06 15:15       ` Danny McClanahan
2024-08-06 15:57         ` Eli Zaretskii
2024-08-07  4:28           ` Danny McClanahan
2024-08-06 18:18         ` Pip Cet
2024-08-06 18:38           ` Eli Zaretskii
2024-08-07  4:23             ` Danny McClanahan
2024-08-07 12:00               ` Eli Zaretskii
2024-08-07 12:43                 ` Helmut Eller
2024-08-07 13:40                   ` Augusto Stoffel
2024-08-07 15:23                     ` Danny McClanahan
2024-08-14  1:32                     ` Stefan Monnier
2024-11-26 18:05                       ` Danny McClanahan
2024-11-26 18:50                         ` Danny McClanahan [this message]
2024-08-07 15:02                 ` Danny McClanahan
2024-08-07 15:23                   ` Eli Zaretskii
2024-08-14  1:25               ` Stefan Monnier
2024-08-07  7:59           ` Danny McClanahan
2024-08-06 12:08     ` Eli Zaretskii
2024-08-01  8:30 ` Andrea Corallo
2024-08-01 10:06   ` Gerd Möllmann
2024-08-06 13:47   ` Danny McClanahan
2024-08-06 13:57     ` Danny McClanahan
2024-08-07  7:21     ` Andrea Corallo
2024-08-07  8:27       ` Danny McClanahan

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='231nVA_JeeFRqN-Jr2qUlIPAwaTNYT2G1qiiSY5Y4hRBFChCiK0sgenqrHcARaGyopcDt5XzTfk63BzPZAs0-8syQ-UDWVqoOz2B3mYrvuY=@hypnicjerk.ai' \
    --to=dmcc2@hypnicjerk.ai \
    --cc=acorallo@gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pipcet@protonmail.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).