Was there a particular reason (aside from access time) you ch=
ose
hash tables instead of a sexp form?
- H=
ashtables have similar constraints as the underlying JSON objects (no dupli=
cate keys, no ordering), so they are a better match.
- Hashtables=
have non-nil empty values. If I had uses alists, I would have had to intro=
duce a separate keyword :json-null for null.
- Hashtables always =
represent maps, but alists are also normal sequences, so users could expect=
that they get translated into arrays instead of objects.
- Using=
only one data structure per JSON object type makes the interface and imple=
mentation simpler.