From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Andy Moreton <andrewjmoreton@gmail.com>,
"30458@debbugs.gnu.org" <30458@debbugs.gnu.org>
Subject: bug#30458: [External] : Re: bug#30458: hash table reverse-lookup (get-keys VALUE TABLE) => KEYS
Date: Thu, 12 Aug 2021 15:08:01 +0000 [thread overview]
Message-ID: <SJ0PR10MB54889B3FFF90F77E6AA60C08F3F99@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <874kbuk9p1.fsf_-_@gnus.org>
> > Still, I would ask to have general reverse-lookup functions
> > for a hash table, as well. Would someone please retitle this
> > bug for that?
>
> We have this now in the form of `map-filter' (and friends),
> so I'm closing this bug report.
It's fine that we have `map-filter' and friends.
But that doesn't really help very directly, or in
terms of discoverability. It's easy to discover
`rassoc', given `assoc' (e.g., just use `apropos',
or look up `assoc' in the manual, or just look up
"association list").
Being able to realize this functionality "in the
form of `map-filter' (& friends)" isn't so helpful.
And has the _doc about hash tables_ been updated
to indicate just how to do a reverse lookup?
Node `Association Lists' of the Elisp manual tells
you about `assoc', `rassoc', and `assq' (and more)
together. Why? Because their doc belongs together.
If a similar/equivalent treatment hasn't been done
for hash tables - provide a direct function and fix
the doc - then I don't consider this bug to have
been fixed. Instead, in that case it's just another
"won't fix".
The aim shouldn't be to find a reason to close bug
reports. The aim should be to fix bugs. If the bug
was really fixed, then thanks! If not, no thanks.
Saying that one can program using this, that, and
the other thing (XYZ "and friends") to work around
the lack of some feature is no replacement for
providing that missing feature directly.
`rassoc' and `rassq' have been in Lisp since about
Day One. There's a reason for that.
prev parent reply other threads:[~2021-08-12 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 17:41 bug#30458: 26.0; `ucs-names': No reverse lookup function now Drew Adams
2018-02-14 19:04 ` Andy Moreton
2018-02-14 21:09 ` Drew Adams
2018-02-15 2:01 ` Noam Postavsky
2021-08-12 14:40 ` bug#30458: hash table reverse-lookup (get-keys VALUE TABLE) => KEYS Lars Ingebrigtsen
2021-08-12 15:08 ` Drew Adams [this message]
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=SJ0PR10MB54889B3FFF90F77E6AA60C08F3F99@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=30458@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=larsi@gnus.org \
/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).