unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: paaguti@gmail.com, emacs-devel@gnu.org
Subject: Re: seq.el and the complexity of Emacs Lisp.
Date: Tue, 07 Nov 2023 22:08:00 -0500	[thread overview]
Message-ID: <E1r0YvA-0000F0-JK@fencepost.gnu.org> (raw)
In-Reply-To: <m24jhzcpwf.fsf@Pro.fritz.box> (message from Gerd Möllmann on Mon, 06 Nov 2023 08:16:48 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > ...you are loosing me here. I'm still wondering what seq/map are good
  > for in the first place. Considering something "cleaner" is just a
  > feeling, isn't it? A feeling I don't share.

I don't concretely know, as I have not used them myself.  But I suppose
that the seq- functions do the same jobs as the cl- sequence functions.

  > > Could we replace all the cl-lib sequence function calls with seq-
  > > calls, in core and GNU ELPA code?  Seq is simpler and cleaner, so that
  > > would be an improvement.  We could keep cl-lib permanently for
  > > compatibility for external code, but it would not need to be loaded
  > > (into Emacs or your brain) very often.

  > But does that really make sense? Using either is somewhat subjective.

It is ok for a decision like this, about which of two alternative
solutions is better, to be somewhat subjective.  But it is clearly
somewhat objective too/

  > Saying lets just drop these in a sec to all package authors seems
  > overreaching.

The concept of "overreach" is not applicable to a technical decision
like this.  This isn't about respecting or not respecting anyone's
personal rights.

Surely we should not accept a moral principle that Emacs should
contain all the alternative solutions that are at least halfway
acceptable.  We must be able to limit what we include.

  > You write like lets just remove cl-lib and forget that is existed.
  > As mentioned elsewhere cl-lib isn't just sequence functions..

That is true.  This would affect the CL sequence functions, of which
it seems many or all are defined in cl-seq.el.

The overall issue concerns the CL functions in general, because of the
way they tend to be alternate versions of important facilities defined
by Emacs Lisp.  Having those sets of alternatives is a kind of bloat.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2023-11-08  3:08 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  8:21 What's missing in ELisp that makes, people want to use cl-lib? Pedro Andres Aranda Gutierrez
2023-11-03  9:27 ` João Távora
2023-11-03 10:43   ` Pedro Andres Aranda Gutierrez
2023-11-03 13:37 ` Gerd Möllmann
2023-11-03 14:27   ` Eli Zaretskii
2023-11-03 15:08     ` Gerd Möllmann
2023-11-03 15:13       ` Eli Zaretskii
2023-11-03 15:30         ` Gerd Möllmann
2023-11-03 15:39           ` Eli Zaretskii
2023-11-03 15:49             ` Gerd Möllmann
2023-11-06  2:27   ` seq.el and the complexity of Emacs Lisp Richard Stallman
2023-11-06  6:51     ` Philip Kaludercic
2023-11-06  7:16     ` Gerd Möllmann
2023-11-07 10:24       ` João Távora
2023-11-09 21:02         ` Jim Porter
2023-11-09 21:20           ` João Távora
2023-11-09 23:49             ` Jim Porter
2023-11-09 23:53               ` Jim Porter
2023-11-10  2:31               ` João Távora
2023-11-10  3:27                 ` Jim Porter
2023-11-10 10:03               ` Alan Mackenzie
2023-11-10 12:01                 ` Eli Zaretskii
2023-11-10 10:13             ` Michael Heerdegen
2023-11-10 10:26               ` João Távora
2023-11-10 13:30                 ` Michael Heerdegen
2023-11-08  3:08       ` Richard Stallman [this message]
2023-11-08  3:08       ` Richard Stallman
2023-11-08  5:31         ` Gerd Möllmann
2023-11-06  8:11     ` Björn Bidar
2023-11-06 12:28     ` Eli Zaretskii
2023-11-06 21:43       ` Emanuel Berg
2023-11-07  5:21         ` tomas
2023-11-07  5:50           ` Emanuel Berg
2023-11-07  6:21           ` Emanuel Berg
2023-11-07 12:02             ` Ihor Radchenko
2023-11-07 12:28               ` Emanuel Berg
2023-11-07 12:20             ` Eli Zaretskii
2023-11-07 12:29               ` Emanuel Berg
2023-11-07 11:58         ` Eli Zaretskii
2023-11-07 12:26           ` Emanuel Berg
2023-11-08  3:08       ` Richard Stallman
     [not found]     ` <874jhz9u8z.fsf@>
2023-11-06 12:35       ` Eli Zaretskii
2023-11-06 12:50         ` Björn Bidar
2023-11-06 21:30           ` Emanuel Berg
2023-11-07  7:35             ` Harald Judt
2023-11-07 10:14               ` Emanuel Berg
2023-11-07 12:26                 ` Harald Judt
2023-11-07 12:38                   ` Ihor Radchenko
2023-11-07 12:58                     ` Eli Zaretskii
2023-11-07 13:50                   ` Emanuel Berg
2023-11-07 14:12                     ` Eli Zaretskii

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=E1r0YvA-0000F0-JK@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=paaguti@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).