[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: map.el and naming
From: |
Nicolas Petton |
Subject: |
Re: map.el and naming |
Date: |
Mon, 02 Mar 2015 14:59:44 +0100 |
Stefan Monnier writes:
>> 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.
>
> Indeed, these names kind of suck. For `map-map-keys', you could use `
> map-keys', tho this name could also be used for a function which just
> returns the list of keys. For `map-map' you could use `map-apply' or
> `map-kv' (for "keys and values").
I used `map-keys' to return the list of keys indeed. I don't really
like `map-kv', seems cryptic to me. `map-apply' could work, but it's
still not as good as `seq-map' for example.
Maybe naming the library map.el isn't a good fit afterall, as map also
refers to mapping. Would anyone have another idea?
Nico
--
Nicolas Petton
http://nicolas-petton.fr
signature.asc
Description: PGP signature
- Re: map.el and naming, Stefan Monnier, 2015/03/02
- Re: map.el and naming,
Nicolas Petton <=
- Re: map.el and naming, Stefan Monnier, 2015/03/02
- Re: map.el and naming, Nicolas Petton, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming, Nicolas Petton, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming, Artur Malabarba, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming, Artur Malabarba, 2015/03/02
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/02
- Re: map.el and naming, Stefan Monnier, 2015/03/02