From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Petton <nicolas@petton.fr>
Cc: emacs-devel@gnu.org
Subject: Re: map.el and naming
Date: Sat, 28 Feb 2015 15:49:55 +0200 [thread overview]
Message-ID: <8361amtabg.fsf@gnu.org> (raw)
In-Reply-To: <87lhji1aw8.fsf@petton.fr>
> From: Nicolas Petton <nicolas@petton.fr>
> Date: Sat, 28 Feb 2015 13:24:55 +0100
>
> I'm working on another library similar to seq.el but for maps (alists
> and hash-tables for now).
>
> I have an issue with naming regarding mapping over keys/values of a
> map. I thought about calling `map-map' the function that would map over
> the keys and values of map, and `map-map-keys' the function that would
> map over the keys of a map, etc.
Are there any reasons why we couldn't have map-keys that could accept
any object where such an operation makes sense? IOW, why do we have
to use different functions for different classes of objects, instead
of having a single polymorphic interface? That would solve the naming
issue as a nice side effect, and more importantly, will allow the
programmer to remember fewer symbols.
next prev parent reply other threads:[~2015-02-28 13:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 12:24 map.el and naming Nicolas Petton
2015-02-28 13:32 ` Bozhidar Batsov
2015-03-03 15:58 ` bburns.km
2015-03-04 7:51 ` Nicolas Petton
2015-03-04 9:38 ` Nic Ferrier
2015-02-28 13:49 ` Eli Zaretskii [this message]
2015-02-28 16:21 ` Artur Malabarba
2015-03-02 5:31 ` Stefan Monnier
2015-03-02 7:38 ` Nicolas Petton
2015-03-02 13:20 ` Eli Zaretskii
2015-03-02 13:26 ` Nicolas Petton
2015-03-02 13:55 ` Eli Zaretskii
2015-03-02 14:33 ` Artur Malabarba
2015-03-02 14:49 ` Eli Zaretskii
2015-03-02 15:08 ` Artur Malabarba
2015-03-02 15:24 ` Stephen J. Turnbull
2015-03-02 16:53 ` Stefan Monnier
2015-03-03 3:14 ` Stephen J. Turnbull
2015-03-03 16:36 ` Stefan Monnier
2015-03-04 2:07 ` Stephen J. Turnbull
2015-03-02 5:29 ` Stefan Monnier
2015-03-02 13:59 ` Nicolas Petton
2015-04-11 0:52 ` Nicolas Petton
2015-04-11 13:53 ` Stefan Monnier
2015-04-11 14:07 ` Nicolas Petton
2015-04-11 13:55 ` Stefan Monnier
2015-04-11 14:11 ` Nicolas Petton
2015-04-11 14:24 ` John Yates
2015-04-11 14:32 ` Dmitry Gutov
2015-04-11 19:54 ` Artur Malabarba
2015-04-12 3:32 ` Stefan Monnier
2015-04-11 14:21 ` Artur Malabarba
2015-04-12 3:25 ` Stefan Monnier
2015-04-11 14:20 ` John Yates
2015-04-11 21:44 ` John Mastro
2015-04-12 3:34 ` Stefan Monnier
2015-04-12 7:12 ` Daniel Colascione
2015-04-12 11:48 ` Stefan Monnier
2015-04-12 11:59 ` Nicolas Petton
2015-04-12 12:53 ` Stefan Monnier
2015-04-12 13:38 ` Stephen J. Turnbull
2015-04-12 14:22 ` Yuri Khan
2015-04-12 14:52 ` Nicolas Petton
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=8361amtabg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).