From: Noam Postavsky <npostavs@gmail.com>
To: "Garreau, Alexandre" <galex-713@galex-713.eu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: dolist considered harmful
Date: Wed, 31 Oct 2018 18:44:54 -0400 [thread overview]
Message-ID: <CAM-tV-8h0kg4ECBfH+B8S-=6iF5Zi9AnYkOWG-2vxyptOg27gw@mail.gmail.com> (raw)
In-Reply-To: <877ehxsrji.fsf@portable.galex-713.eu>
On Wed, 31 Oct 2018 at 18:10, Garreau, Alexandre <galex-713@galex-713.eu> wrote:
>
> On 2018-10-30 at 14:39, Stefan Monnier wrote:
> > All this pcase-dolist discussion made me take a second look at dolist
> > and now I wondering whether we should keep it:
>
> This is still extreme: I never saw anyone suggesting to remove anything
> about pcase or its derivative… but I can get quite distracted sometimes
> so maybe I missed it.
Not pcase, but Alan talked about removing pcase-dolist and other derivatives:
https://lists.gnu.org/archive/html/emacs-devel/2018-10/msg00664.html
If we can't get quality doc strings for pcase-dolist and friends, I say
we should remove them from Emacs. There are only around 30 occurrences
of pcase-dolist.
> (btw is emacs tail-recursive?),
Nope. Which is why recursion is not idiomatic.
> I used `dolist', I first wanted to use recursion before someone noticed
> me it was unnatural / strang / unidiomatic in elisp to do that,
next prev parent reply other threads:[~2018-10-31 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 18:39 dolist considered harmful Stefan Monnier
2018-10-30 19:31 ` Eli Zaretskii
2018-10-30 23:24 ` Jay Kamat
2018-10-30 23:29 ` Noam Postavsky
2018-10-30 23:47 ` Drew Adams
2018-10-31 22:02 ` Garreau, Alexandre
2018-10-31 22:44 ` Noam Postavsky [this message]
2018-10-31 23:01 ` Garreau, Alexandre
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='CAM-tV-8h0kg4ECBfH+B8S-=6iF5Zi9AnYkOWG-2vxyptOg27gw@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
--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 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.