From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Philipp Stephani" <p.stephani2@gmail.com>,
"Mattias Engdegård" <mattiase@acm.org>,
"Lars Ingebrigtsen" <larsi@gnus.org>,
"Nicolas Petton" <nicolas@petton.fr>,
"47425@debbugs.gnu.org" <47425@debbugs.gnu.org>
Subject: bug#47425: 26.3; `plist-get', `plist-put' should accept a TEST function
Date: Mon, 27 Jun 2022 17:07:16 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883F15FCF4A08B0A5FB0E9F3B99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <jwvsfnq5eiz.fsf-monnier+emacs@gnu.org>
> > Plists with, e.g., string keys aren't uncommon
>
> Really? Can you give examples?
Maybe I could, but I won't try. I take it that
you don't think so. That's fine.
My expectation is that more users nowadays may
be inclined to use string keys than in the past,
because (as I said) of the influence of things
like JSON. This enhancement request is to cater
to what I expect will not be all that uncommon.
And there may be more and more use of conversion
of alists (which do often have nonsymbol keys)
to plists. For whatever reasons (good & bad).
Note too, BTW, that (not uncommon) != common.
___
CLTL2, "The Property List" says, in passing,
that `symbol-plist' keys are "typically" symbols.
It doesn't say that they _are_ symbols.
And it doesn't say anywhere that they need to
be distinguishable with just `eq'.
In any case, I'll grant you that using symbol
keys _is_ common. (The same is true of alist
keys, BTW.)
___
BTW, CLTL2 also points to this as the essential
difference between a plist and an alist:
a property list is an object with a unique
identity; the operations for adding and
removing property-list entries are destructive
operations that alter the property list rather
than making a new one. Association lists, on
the other hand, are normally augmented
non-destructively (without side effects) by
adding new entries to the front (see acons and
pairlis).
No mention of plist keys being symbols.
However, it's also true that CL defines `remprop'
as using `eq'.
next prev parent reply other threads:[~2022-06-27 17:07 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
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 [this message]
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=SJ0PR10MB54883F15FCF4A08B0A5FB0E9F3B99@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=47425@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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).