From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Nicolas Petton <nicolas@petton.fr>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
dalanicolai <dalanicolai@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
47368@debbugs.gnu.org
Subject: bug#47368: 28.0.50; map-elt returns nil without "deprecated" TESTFN
Date: Sat, 27 Mar 2021 20:37:23 +0000 [thread overview]
Message-ID: <87r1k0nxj0.fsf@tcd.ie> (raw)
In-Reply-To: <87y2e9zqt2.fsf@tcd.ie> (Basil L. Contovounesios's message of "Fri, 26 Mar 2021 18:57:13 +0000")
Trying the CC again, this time with a hopefully correct address.
Sorry about the noise.
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> What's a good way to solve this? Obviously the map abstraction doesn't
>>> fit so super well for alists because unlike the other map type alists
>>> don't know "their" test function. But disallowing alists that don't
>>> test with `eq' seems an unnecessary restriction. Can we say that the
>>> argument is allowed only for alists?
>>
>> How 'bout always using `equal`?
>
> No objections here. CCing Nicolas in case he has any comments.
>
> Just some code archaeology for more context:
>
> - Pre-Emacs-25 map-elt used assoc.
> - Emacs 25 map-elt used alist-get without TESTFN.
> - Emacs 26 map-elt gained TESTFN at the same time that alist-get did,
> in https://bugs.gnu.org/27584.
> - Emacs 27 deprecated map-elt's TESTFN.
--
Basil
next prev parent reply other threads:[~2021-03-27 20:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 22:52 bug#47368: 28.0.50; map-elt returns nil without "deprecated" TESTFN dalanicolai
2021-03-24 23:24 ` Basil L. Contovounesios
2021-03-25 2:39 ` Michael Heerdegen
2021-03-25 14:48 ` dalanicolai
2021-03-25 15:33 ` bug#47368: [External] : " Drew Adams
2021-03-26 18:47 ` Basil L. Contovounesios
2021-03-26 20:04 ` Drew Adams
2021-03-26 20:23 ` Basil L. Contovounesios
2021-03-26 22:40 ` Drew Adams
2021-03-26 22:59 ` Basil L. Contovounesios
2021-03-26 3:59 ` Michael Heerdegen
2021-03-26 7:38 ` dalanicolai
2021-03-26 13:31 ` Stefan Monnier
2021-03-26 15:32 ` dalanicolai
2021-03-26 18:57 ` Basil L. Contovounesios
2021-03-26 23:18 ` Michael Heerdegen
2021-03-27 20:37 ` Basil L. Contovounesios [this message]
2021-03-26 23:23 ` Michael Heerdegen
2021-03-26 18:58 ` Basil L. Contovounesios
2021-07-21 15:34 ` Adam Porter
2021-07-22 2:15 ` Michael Heerdegen
2021-07-31 2:15 ` Michael Heerdegen
2021-09-13 14:06 ` Adam Porter
2021-09-14 14:40 ` Michael Heerdegen
2021-09-14 20:22 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 0:48 ` Michael Heerdegen
2021-09-15 9:26 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 12:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 21:53 ` Michael Heerdegen
2021-09-15 12:50 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 21:55 ` Michael Heerdegen
2021-09-21 12:42 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87r1k0nxj0.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=47368@debbugs.gnu.org \
--cc=dalanicolai@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@petton.fr \
/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).