News for hackers. Stuff that matters.
Re:A History of Clojure [pdf] by didibus on Friday June 05, 2020 @02:56AM (#23425795)
If you read Rich's paper, there's a section where it says:

> maps were built behind several abstractions. Thus, maps can start with a representation optimized for small maps and switch to a representation optimized for large collections if and when they ‘grow’ beyond a certain size.

Which is pretty cool, because basically the Clojure version of your code abstracts over alist-hash-table and alist, and the most optimal type of concrete map will automatically be created based on the size of the map you are asking to create.

Re:A History of Clojure [pdf] by jlarocco on Friday June 05, 2020 @05:31AM (#23426593)
There's actually an implementation of the same HAMT data structure that Clojure uses available in QuickLisp and on GitHub: https://github.com/danshapero/cl-hamt/

Technically, since the hash-table implementation isn't specified in the CL standard an implementation could use a HAMT for the built-in hash tables, but I don't think any do.

Re:A History of Clojure [pdf] by didibus on Friday June 05, 2020 @01:39PM (#23431377)
The construction of a Map is abstract in Clojure. The concrete type of Map you get is not something you specify. This isn't related to the HAMT per say.

So what I mean is Clojure will use an array backed map when you ask it to construct a small map, and it will give you a HAMT backed map when the map is large.

This is true as well as you add elements to a map, Clojure might automatically promote the map from an array map to a HAMT as its size grows.