From: John Mastro <john.b.mastro@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>
Subject: Re: map.el and naming
Date: Sat, 11 Apr 2015 14:44:25 -0700 [thread overview]
Message-ID: <CAOj2CQTCNq6pOfUAd+E4i6gNk3YkjXHwT9sfq=TpjDY0BAhG=g@mail.gmail.com> (raw)
In-Reply-To: <874monpju0.fsf@petton.fr>
Nicolas Petton <nicolas@petton.fr> wrote:
> > 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.
> >
> > This is really ugly to my eyes, as there is map the name and map the
> > verb. Does anyone have a better idea?
>
> I'm back with this issue. Since I have "map" both as a verb and as a
> name, and because I don't want to call "mapping" something else, I think
> I'll go with renaming the library.
How about "mapping.el"? Not a verb, as in "mapping over a list", but
rather a noun, as in "a hash table (or an association list) is a mapping
from keys to values."
So you would have e.g. `mapping-map' and `mapping-map-keys'. It loses
some of the nice concision of "map" (and of course "map" still shows up
twice), but it doesn't seem too bad to me.
--
john
next prev parent reply other threads:[~2015-04-11 21:44 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOj2CQTCNq6pOfUAd+E4i6gNk3YkjXHwT9sfq=TpjDY0BAhG=g@mail.gmail.com' \
--to=john.b.mastro@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.