From: Drew Adams <drew.adams@oracle.com>
To: Nicolas Petton <nicolas@petton.fr>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: 28753@debbugs.gnu.org
Subject: bug#28753: 25.3; Functions to get alist from hash table and vice versa
Date: Mon, 6 Nov 2017 08:19:16 -0800 (PST) [thread overview]
Message-ID: <f3a6a5d9-b9bb-4bbf-a956-6af89151b389@default> (raw)
In-Reply-To: <52a5f9a9-2fd9-49a6-9dd1-849f3c18b519@default>
> It's great to have abstract, general-purpose
> functions that handle maps, sequences, streams,
> etc. But not all such things are handled the
> same way in Lisp code. An alist is itself quite
> general, so it can be and is used in different
> ways in different programs. There is no single,
> simple mapping from an arbitrary alist to a hash
> table, I think.
>
> We can provide a general-purpose function that
> chooses just one kind of mapping from an alist
> to, e.g., a hash table. But I'm guessing that we
> should also provide a function that gives you more
> control over the conversion mapping. IOW, maybe
> both a `map-into' kind of general-purpose behavior
> and a more specific `alist-to-hash-table' kind of
> behavior.
>
> (But for the time being, `map-into' is only for
> list <-> hash table, so for the time being it
> seems less useful than the more specific
> function.)
Any news on this? There is no general, abstract
solution proposed, so far, to meet the needs met
by the specific alist <-> hash-table code I sent.
Should we not add that code or similar to Emacs?
next prev parent reply other threads:[~2017-11-06 16:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 0:25 bug#28753: 25.3; Functions to get alist from hash table and vice versa Drew Adams
2017-10-09 13:20 ` Michael Heerdegen
2017-10-09 14:11 ` Drew Adams
2017-10-11 16:42 ` Drew Adams
[not found] ` <87wp4038m0.fsf@web.de>
2017-10-12 13:27 ` Nicolas Petton
2017-10-12 13:46 ` Michael Heerdegen
2017-10-12 14:36 ` Drew Adams
2017-11-06 16:19 ` Drew Adams [this message]
2017-11-07 0:46 ` Noam Postavsky
2017-11-07 2:24 ` Drew Adams
2017-11-07 2:51 ` Noam Postavsky
2017-11-07 13:28 ` Michael Heerdegen
2017-12-30 20:40 ` Philipp Stephani
2017-12-30 21:08 ` Drew Adams
2017-12-30 21:15 ` Philipp Stephani
2017-10-12 15:56 ` Noam Postavsky
2017-10-12 13:30 ` Nicolas Petton
2022-04-22 13:18 ` Lars Ingebrigtsen
2022-04-22 15:21 ` Drew Adams
2017-12-30 21:26 ` Philipp Stephani
2017-12-31 0:01 ` Drew Adams
2018-03-04 19:17 ` Philipp Stephani
2018-03-05 0:01 ` 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=f3a6a5d9-b9bb-4bbf-a956-6af89151b389@default \
--to=drew.adams@oracle.com \
--cc=28753@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--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).