Re: map.el documentation

[Augusto Stoffel]

On Fri, 24 Jan 2025 at 17:30, Robert Pluim wrote:

>     Augusto> At first I thought that would be a bad idea.  However, if one 
> actually
>     Augusto> cares about speed and is fine with consing a possibly repeated 
> key, then
>     Augusto> arguably one shouldn't use map.el -- there already is cons for 
> that.  So
>     Augusto> it makes sense to use map.el to supply an implementation of the
>     Augusto> operation you want.
>
> Yes. If we worry about backwards compatibility we can call it
> `map-insert!'

Please don't do that :-).

map-insert! should be reserved for the destructive version.

>     Augusto> (BTW, I don't quite see an use for the polymorphism aspect of 
> map.el and
>     Augusto> the only reason I would use that library is for less common 
> operations
>     Augusto> on map-like things whose type I know for sure.  For example
>     Augusto> map-nested-elt is a nice function.)
>
> I can see a use for it when dealing with both plists and alists and
> not wanting to worry about the differences. hash-tables are a natural
> extension, but arrays are not.

Right, the array specialization is weird and should probably be
deprecated.