From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philipp <p.stephani2@gmail.com>
Cc: Nicolas Petton <nicolas@petton.fr>,
47425@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#47425: 26.3; `plist-get', `plist-put' should accept a TEST function
Date: Sun, 28 Mar 2021 21:27:09 +0200 [thread overview]
Message-ID: <87v99bnkoi.fsf@gnus.org> (raw)
In-Reply-To: <0EBFBE59-A4C2-4C61-AD1B-A66E8B5F99CF@gmail.com> (Philipp's message of "Sun, 28 Mar 2021 21:20:53 +0200")
Philipp <p.stephani2@gmail.com> writes:
> I'm not a fan of this since it would mean that these functions will no
> longer be side-effect-free. Adding a function argument to a function
> means that the function can no longer really promise anything, so it
> leads to code that's harder to reason about.
`plist-put' already mutates state (of the plist), so it's not
side-effect-free...
The other ones are, though. But... I'm not sure that's really much of
a concern in practice. (And Emacs should be able to reason about the
function, still, if the predicate passed in is side effect free, but I
guess we don't have the machinery for that in place?)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-28 19:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 22:13 bug#47425: 26.3; `plist-get', `plist-put' should accept a TEST function Drew Adams
2021-03-26 22:16 ` Drew Adams
2021-03-27 7:16 ` Jean Louis
2021-03-28 13:12 ` Lars Ingebrigtsen
2021-03-28 16:43 ` bug#47425: [External] : " Drew Adams
2021-03-28 19:20 ` Philipp
2021-03-28 19:27 ` Lars Ingebrigtsen [this message]
2022-06-27 10:22 ` Lars Ingebrigtsen
2022-06-27 11:31 ` Mattias Engdegård
2022-06-27 11:43 ` Lars Ingebrigtsen
2022-06-27 12:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 12:27 ` Mattias Engdegård
2022-06-27 12:44 ` Lars Ingebrigtsen
2022-06-27 13:28 ` Mattias Engdegård
2022-06-27 13:35 ` Lars Ingebrigtsen
2022-06-27 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 15:18 ` Lars Ingebrigtsen
2022-06-27 14:39 ` Drew Adams
2022-06-27 14:39 ` Drew Adams
2022-06-27 12:41 ` Lars Ingebrigtsen
2022-06-27 14:39 ` Drew Adams
2022-06-27 14:39 ` Drew Adams
2022-06-27 15:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 17:07 ` Drew Adams
2022-06-27 17:19 ` Mattias Engdegård
2022-06-27 17:22 ` Lars Ingebrigtsen
2022-06-28 15:23 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-28 15:40 ` Lars Ingebrigtsen
2022-06-29 3:33 ` bug#47425: 26.3; `plist-get', `plist-put' and proposed " Richard Stallman
2022-06-29 5:11 ` Drew Adams
2022-06-30 3:10 ` Richard Stallman
2022-06-27 17:41 ` bug#47425: 26.3; `plist-get', `plist-put' should accept a " 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=87v99bnkoi.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47425@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@petton.fr \
--cc=p.stephani2@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).