Re: map.el and naming

[Eli Zaretskii]

> From: Nicolas Petton <address@hidden>
> Cc: Nicolas Petton <address@hidden>, address@hidden
> Date: Mon, 02 Mar 2015 14:26:43 +0100
> 
> > 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.

But polymorphism _is_ about using the same APIs for treating different
objects.  Do any of the operations in seq.el make sense with the
objects you meant to handle in map.el?  If so, it could make sense to
have them treated by the same API.

Anyway, if the above doesn't sound right, I can suggest maps.el and
correspondingly maps-map-key etc.