Open cebtenzzre opened 6 years ago
Huh, I hadn't realized the latest JSON RFC relaxed that requirement! I'm a little nervous about adding unilateral support. Many parsers still maintain that restriction, I believe. We should probably add an option to allow the root to have any value type.
All tests from nst/JSONTestSuite with a single value (string, number, boolean, or null) at the root fail with an error:
One example is y_structure_lonely_int.json:
If it weren't for this issue, then this parser would (AFAIK) be 100% conformant to RFC 8259.