[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:26:43 +0100 |
Eli Zaretskii writes:
> Then why are you writing a separate library, which is "similar to
> seq.el but for maps"? Why not have a single library that handles all
> of these objects: lists, strings, vectors, alists, and hash-tables?
Isn't it better to treat sequences and maps separate kind of
collections? They are IMHO too different to be both in the same
library.
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, 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 <=
- 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
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/02
- Re: map.el and naming, Stefan Monnier, 2015/03/03
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/03
Re: map.el and naming, bburns.km, 2015/03/03