all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Installing cond* in core
Date: Sun, 28 Jan 2024 15:58:19 +0000	[thread overview]
Message-ID: <ZbZ5m1AO5Ltqglvc@ACM> (raw)
In-Reply-To: <CADwFkmnMLrZnQHo0u0oAXrEzuBsMmxo_9+wd6dXMaijUSWE7cA@mail.gmail.com>

Hello, Stefan.

On Sat, Jan 27, 2024 at 16:26:17 -0800, Stefan Kangas wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > Can you further confirm that there will be no technical advantages given
> > to pcase over cond*?

> I see cond* as an alternative to pcase for those that prefer it.
> This is one consequence of deciding not to get rid of pcase.

> > In particular, that condstar.el will be in lisp/emacs-lisp,

> We didn't discuss that.  I'd put it in lisp/, myself.

That would make it unusable early in the bootstrap, putting it at a
disadvantage to pcase.

> > and that it will be available from early mid-bootstrap onwards, just
> > as pcase is?

> We didn't discuss that.  It sounds like a separate change from adding
> cond* to core, and I'm not sure it makes sense to commit to it off-hand,
> without first understanding the details.

> In general, there is no point to loading something early unless it is
> used early.  Do you have something more specific in mind?

Yes.  I outlined a few days ago my idea of tidying up the bootstrap
process by using cond* in macroexp.el, thus allowing the files loaded by
loadup.el to be in a more natural order.  This idea was vetoed by Eli,
at least for the moment.  But it seems like a good idea not to rule out
similar changes in the future.

> > On this point, it's worth noting that pcase was silently slipped into
> > Emacs in the dead of night without any public discussion, and was then
> > widely proliferated through working code, again without discussion.
> > That has relevance to "alienation", and goes some way towards explaining
> > my attitude towards cond* and pcase.

> I can't speak to that, as I wasn't around.

> I would propose that we start looking forward, and go back to working on
> the things that we enjoy and find interesting.  That's likely to be more
> productive than discussing the details of how things happened or didn't
> happen 14 years ago.

The events of 14 years ago have a profound influence on the present and
future.  I'm somewhat disappointed that the solution you've come up with
for cond* is not going to help me at all, though I understand how and
why you made it.  It's basically leave things as they are and ignore
cond*.  In ten years time, I'm still going to be faced with inscrutable
pcases when debugging code, and that will still slow me down just as
much as it does today.

-- 
Alan Mackenzie (Nuremberg, Germany).



  parent reply	other threads:[~2024-01-28 15:58 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 21:36 Installing cond* in core Stefan Kangas
2024-01-27 23:33 ` Alan Mackenzie
2024-01-28  0:26   ` Stefan Kangas
2024-01-28  2:43     ` Po Lu
2024-01-28  6:46       ` Eli Zaretskii
2024-01-28  7:21         ` Po Lu
2024-01-28  7:32           ` Eli Zaretskii
2024-01-28  6:14     ` Eli Zaretskii
2024-01-28 15:58     ` Alan Mackenzie [this message]
2024-01-28  6:09   ` Eli Zaretskii
2024-01-28 12:38     ` Alan Mackenzie
2024-01-28 13:02       ` Dmitry Gutov
2024-01-28 13:38         ` Alan Mackenzie
2024-01-28 13:48           ` Dmitry Gutov
2024-01-28 14:32             ` Alan Mackenzie
2024-01-28 16:54               ` Dmitry Gutov
2024-01-28 19:14                 ` Alan Mackenzie
2024-01-28 19:26                   ` Eli Zaretskii
2024-01-28 20:43                   ` Dmitry Gutov
2024-01-30  3:56                 ` Richard Stallman
2024-01-28 13:19       ` Emanuel Berg
2024-01-28 14:18       ` Eli Zaretskii
2024-01-28 15:26         ` Alan Mackenzie
2024-01-28 15:40           ` Eli Zaretskii
2024-01-30  3:57             ` Richard Stallman
2024-01-28  4:28 ` Stefan Monnier via Emacs development discussions.
2024-01-30  3:58   ` Richard Stallman
2024-01-30 14:33     ` Stefan Monnier
2024-02-02  3:39       ` Richard Stallman
2024-02-02 13:17         ` Stefan Monnier
2024-02-02 15:24           ` Alan Mackenzie
2024-02-02 18:50             ` Stefan Monnier
2024-02-04  4:47               ` Richard Stallman
2024-02-04 14:12                 ` Stefan Monnier
2024-02-06  3:49                   ` Richard Stallman
2024-02-05  3:33           ` Richard Stallman
2024-02-05 12:39             ` Stefan Monnier
2024-03-13  2:27               ` Richard Stallman
2024-03-13  3:05                 ` Stefan Monnier
2024-03-16  1:45                   ` Richard Stallman
2024-03-16 16:15                     ` Stefan Monnier
2024-03-18  2:42                       ` Richard Stallman
2024-03-18  3:06                         ` Stefan Monnier
2024-03-19  9:19                           ` Peter Hull
2024-03-20 22:40                           ` Richard Stallman
2024-03-20 22:54                             ` Stefan Monnier
2024-01-28 14:28 ` Emanuel Berg
2024-01-30  3:58 ` Richard Stallman
2024-01-30 13:04   ` Eli Zaretskii
2024-03-16 20:53 ` Lynn Winebarger
2024-03-18  2:41   ` Richard Stallman
2024-03-19 19:48     ` Lynn Winebarger

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=ZbZ5m1AO5Ltqglvc@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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.