It's not very critical because it's just JSON.jl failing to handle bad JSON gracefully. But, when parsing very large JSON and trying to see what the error is, this becomes pretty frustrating because it just gives a byte-offset into the file that I need to scan to.
The following misformed JSON (missing a comma between fields) is supposed to give an error like this:
But with the right multibyte UTF-8 characters in the right places, it throws an error while trying to throw the error:
It's not very critical because it's just JSON.jl failing to handle bad JSON gracefully. But, when parsing very large JSON and trying to see what the error is, this becomes pretty frustrating because it just gives a byte-offset into the file that I need to scan to.