Subject: bug#58950: [PATCH] * lisp/subr.el (buffer-match-p): Optimise performance

From: Mattias Engdegård <[email-masked]>
Date: Fri, 6 Jan 2023 12:17:52 +0100

5 jan. 2023 kl. 13.55 skrev Dmitry Gutov <[email-masked]>:

> I'm not sure how we'd reach the same goals with plain old Elisp (structured editing in particular -- in Customize).

No enemy of little DSLs in principle but is that structural editing the main rationale now?

(I wish we had (byte-)compiled elisp functions carrying their own source, either as s-exp, string of formatted source text, or source file reference -- that would allow for sensible editing in Customise without performance penalty. But Santa gave me a wool jumper instead, that's nice too.)

Regarding buffer-match-p, the fact that `not` actually means `nor` is a bit odd (we don't do that elsewhere), as well as arbitrary (why not `nand` etc) and undocumented. And like all the rest of the machinery, untested.