Well, as a hobbyist programmer, this makes more sense to me anyway. If users don't want the behavior of using `equal` then they could just as well use `alist-get`.

I hope you don't mind if I write down some thoughts (and macro's) I have on my mind.

Personally, I think it would be great for growing the community, if emacs-lisp got more approachable (in the direction of python).

I actually got here because, as an exercise, I was trying to implement Norvig's sudoku solver in emacs-lisp, which was a quite frustrating exercise (this is no complaint, but just a fact).

I think it would be great if emacs-lisp could look, and become readable and usable, more like that (in which map.el and seq.el are doing a very nice job of course). So that emacs-lisp could actually

become a nice and friendly teaching language, which is equally fun to script in as in python.

Actually, I got the feeling that it would be nice to have list-comprehension like syntax also. Therefore, I tried to create some general `array` and `table` macro's here (which is my first macro exercise ever).

As it is just an exercise it is undocumented, but you can very easily get the idea from looking at the (commented out) tests at the bottom of that file. Also, from looking at map.el, I assume I should probably

implement it using cl-defgeneric.

Haha... sorry for the elaborate answer.  You can neglect most of this message, but maybe someone is interested and shares some of these ideas (or likes the idea of these macro's). I just couldn't resist to share these thoughts...