Thanks again for your feedback, Dmitry.
Yes, maybe they should. The only drawback I see is that 'json-read' then
needs to accept an optional parameter, which is the JSON key of the
current element.
A revised patch implementing your suggestion is attached.
Benchmarks follow below, with the usual setup!
Before the patch:
(benchmark-run 100 (json-read-from-string huge-json))
⇒ (18.782874379000003 1007 5.674178575000008)
After the patch:
(benchmark-run 100 (json-read-from-string huge-json))
⇒ (18.233328517999997 1007 4.907621599000008)
-- Simen