Stack overflow with large json files

Nobody has claimed this yet.

Recently I experimented with this library as both a native compilation target, as well as through jsoo, and on the jsoo side, I hit a stack overflow when running the code in the browser. I was able to get around the problem by converting the data file to sexp, but I figured I'd report the issue anyways.

Start by reproducing the stack overflow with a large JSON file in the jsoo browser environment described in the issue, and compare it with the reported sexp workaround. The payload names no source files, tests, parser entry point, or concrete input, so those would need to be located before implementation. Done means the large-file case no longer overflows the stack in the affected environment, with a regression test if the project provides a suitable test location.

Written by the indexing model from the issue text.