From: Alan Mackenzie <acm@muc.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: "João Távora" <joaotavora@gmail.com>,
"Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Richard Stallman" <rms@gnu.org>,
paaguti@gmail.com, emacs-devel@gnu.org
Subject: Re: seq.el and the complexity of Emacs Lisp.
Date: Fri, 10 Nov 2023 10:03:48 +0000 [thread overview]
Message-ID: <ZU4ABOGkpJtnJzuy@ACM> (raw)
In-Reply-To: <656f8d5f-2850-062c-1b38-3b50367c64d5@gmail.com>
Hello, Jim.
On Thu, Nov 09, 2023 at 15:49:01 -0800, Jim Porter wrote:
> On 11/9/2023 1:20 PM, João Távora wrote:
> > Examples could be an implementation of lazy sequences
> > for example. So it stands to reason that there's no (obvious) reason
> > to preload seq.el,
> In fact, I was considering adding support to seq.el for generators,
> which we could consider a kind of lazy sequence. I'm not entirely sure I
> *need* it yet, but it could make a few things in Eshell easier.
Please don't. This would be yet one more unnecessary complicated
abstraction for which future maintainers would curse you for introducing.
I don't know what a "generator" is, exactly, but it would likely involve
a plethora of backticks, funcalls, generic functions, and the like, all
things which make debugging difficult, if not very difficult.
The Subject: line of this thread mentions complexity. This is something
we should be trying to reduce in Emacs, not increase.
[ .... ]
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-11-10 10:03 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 [this message]
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
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=ZU4ABOGkpJtnJzuy@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=joaotavora@gmail.com \
--cc=jporterbugs@gmail.com \
--cc=paaguti@gmail.com \
--cc=rms@gnu.org \
/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).