From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25929@debbugs.gnu.org, Nicolas Petton <nicolas@petton.fr>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#25929: 25.2; map-delete doesn't delete permanently 1st alist elt
Date: Wed, 22 Mar 2017 12:55:35 +0100 [thread overview]
Message-ID: <878tnxa5l4.fsf@drachen> (raw)
In-Reply-To: <m3lgrytlb6.fsf@stories> (Lars Ingebrigtsen's message of "Tue, 21 Mar 2017 21:41:01 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> If MAP isn't a symbol, then map-delete could avoid doing the setf,
> couldn't it?
>
> I think that should make for a pretty useful form. You can both say
>
> ...
> (map-delete foo 'bar)
> ...
>
> and
>
> (setq foo (cons (map-delete (get-a-list) 'bar) 'zot))
>
> and not be surprised at the results. It's certainly more fun than the
>current (setq foo (delete 'bar foo)) we have all over the place, even
>if it's something of a departure from how functions like this has
>traditionally worked in various Lisps.
So your suggestion is, with other words, that
(1) (map-delete EXPR 'bar)
is implicitly transformed into
(2) (cl-callf map-delete EXPR 'bar)
when EXPR is a valid place expression.
That's a relatively small gain, and some people might prefer the
explicit form (2) for readability.
OTOH, without such magic, we can avoid making `map-delete' a macro.
Personally I prefer this simpler approach.
Regards,
Michael.
next prev parent reply other threads:[~2017-03-22 11:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 7:17 bug#25929: 25.2; map-delete doesn't delete permanently 1st alist elt Tino Calancha
2017-03-02 8:56 ` Nicolas Petton
2017-03-02 10:59 ` Nicolas Petton
2017-03-02 11:30 ` Tino Calancha
2017-03-02 12:27 ` Nicolas Petton
2017-03-02 12:34 ` Nicolas Petton
2017-03-02 13:34 ` Tino Calancha
2017-03-02 15:12 ` Stefan Monnier
2017-03-04 0:04 ` Michael Heerdegen
2017-03-04 0:16 ` Michael Heerdegen
2017-03-21 20:41 ` Lars Ingebrigtsen
2017-03-22 11:55 ` Michael Heerdegen [this message]
2017-03-22 12:01 ` Lars Ingebrigtsen
2017-03-22 12:56 ` Noam Postavsky
2017-03-22 13:31 ` Lars Ingebrigtsen
2017-03-22 14:43 ` Michael Heerdegen
2017-03-22 17:04 ` Stefan Monnier
2017-03-22 17:23 ` Lars Ingebrigtsen
2017-03-22 20:31 ` Stefan Monnier
2017-03-22 17:02 ` Stefan Monnier
2017-03-29 15:25 ` bug#25929: 25.2; plists and map-* Lars Ingebrigtsen
2017-03-29 15:36 ` Nicolas Petton
2017-03-21 11:35 ` bug#25929: 25.2; map-delete doesn't delete permanently 1st alist elt Nicolas Petton
2017-03-21 15:11 ` Stefan Monnier
2017-03-21 18:06 ` Nicolas Petton
2017-03-21 20:29 ` Stefan Monnier
2017-04-26 7:58 ` Nicolas Petton
2017-03-02 12:36 ` npostavs
2017-03-02 12:45 ` Nicolas Petton
2022-04-26 13:34 ` Lars Ingebrigtsen
2022-04-28 3:17 ` Richard Stallman
2022-04-28 16:00 ` Drew Adams
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=878tnxa5l4.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=25929@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@petton.fr \
--cc=tino.calancha@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).