From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: lekktu@gmail.com, joaotavora@gmail.com, juri@linkov.net,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: cl-lib warnings
Date: Fri, 23 Dec 2022 09:30:07 +0200 [thread overview]
Message-ID: <83bknu8tmo.fsf@gnu.org> (raw)
In-Reply-To: <B4B0311F-9198-4D65-8C2B-F25F6BBE310B@gmail.com> (message from Yuan Fu on Thu, 22 Dec 2022 14:24:02 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Thu, 22 Dec 2022 14:24:02 -0800
> Cc: Juanma Barranquero <lekktu@gmail.com>,
> joaotavora@gmail.com,
> juri@linkov.net,
> monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
>
> > I'm afraid if we preload cl-lib, that would open the gates of hell
> > whereby all of our code will be rewritten in cl-lib dialect that is
> > (at least for me) much harder to read and maintain. So maybe wait
> > until I'm safely dead (at least as far as Emacs is concerned) before
> > doing that.
> >
>
> Wait, what constitutes of cl-lib dialect? Do you mean things like cl-defun? I hope using cl-loop and cl-reduce, cl-remove-if and the like doesn’t make code harder to read.
Yes, cl-loop is one of the worst offenders in my eyes. If I want to
use Fortran or C, I will use Fortran or C; I don't want to see Fortran
for-loops in Emacs Lisp.
next prev parent reply other threads:[~2022-12-23 7:30 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvv8mc4eax.fsf@iro.umontreal.ca>
[not found] ` <86o7s3lsnx.fsf@mail.linkov.net>
2022-12-20 18:42 ` cl-lib warnings (was: bug#60102: Move gv-expander of substring to cl-lib) Stefan Monnier
2022-12-21 8:37 ` cl-lib warnings Juri Linkov
2022-12-21 12:45 ` Eli Zaretskii
2022-12-21 12:57 ` João Távora
2022-12-21 13:47 ` Eli Zaretskii
2022-12-21 14:04 ` João Távora
2022-12-21 14:20 ` Eli Zaretskii
2022-12-21 14:35 ` João Távora
2022-12-21 14:50 ` Juanma Barranquero
2022-12-21 14:55 ` João Távora
2022-12-21 14:57 ` Juanma Barranquero
2022-12-21 15:08 ` João Távora
2022-12-26 3:13 ` Milan Glacier
2022-12-26 15:10 ` João Távora
2022-12-26 23:48 ` Milan Glacier
2022-12-27 0:05 ` João Távora
2022-12-27 3:43 ` Tim Cross
2022-12-27 10:16 ` Lynn Winebarger
2022-12-27 13:00 ` Stefan Kangas
2022-12-21 17:14 ` Eli Zaretskii
2022-12-21 22:33 ` Juanma Barranquero
2022-12-22 7:13 ` Eli Zaretskii
2022-12-22 7:23 ` Juanma Barranquero
2022-12-22 8:53 ` Eli Zaretskii
2022-12-22 22:24 ` Yuan Fu
2022-12-22 23:56 ` Stefan Monnier
2022-12-23 7:30 ` Eli Zaretskii [this message]
2022-12-23 23:42 ` Yuan Fu
2022-12-24 0:24 ` Juanma Barranquero
2022-12-24 14:08 ` Stefan Monnier
2022-12-24 14:39 ` Juanma Barranquero
2022-12-24 19:13 ` Tomas Hlavaty
2022-12-24 0:26 ` João Távora
2022-12-24 10:33 ` Philip Kaludercic
2022-12-24 11:01 ` João Távora
2022-12-26 0:11 ` cl-loop and plists vs alists Philip Kaludercic
2022-12-26 0:35 ` João Távora
2022-12-26 21:06 ` Bob Rogers
2022-12-24 22:59 ` cl-lib warnings Sean Whitton
2022-12-25 1:21 ` Stefan Monnier
2022-12-25 2:39 ` package-initialize was " T.V Raman
2022-12-25 4:11 ` T.V Raman
2022-12-26 0:01 ` Stefan Monnier
2022-12-26 2:18 ` T.V Raman
2022-12-25 7:02 ` tomas
2022-12-25 9:55 ` João Távora
2022-12-25 11:33 ` tomas
2022-12-26 4:47 ` Sean Whitton
2022-12-24 6:40 ` Eli Zaretskii
2022-12-24 13:01 ` Dmitry Gutov
2023-01-06 5:40 ` Sean Whitton
2023-01-06 7:34 ` Eli Zaretskii
2023-01-06 17:58 ` Sean Whitton
2023-01-06 18:14 ` Eli Zaretskii
2023-01-06 19:03 ` Sean Whitton
2023-01-06 19:45 ` Eli Zaretskii
2022-12-21 14:15 ` Eli Zaretskii
2022-12-21 17:53 ` Stefan Monnier
2022-12-24 22:55 ` Sean Whitton
2022-12-25 7:05 ` tomas
2022-12-25 8:29 ` Juri Linkov
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=83bknu8tmo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).