@cryptix

But I really need to find a framing for this that won’t ruint my weekend

You are getting paid.

=P

I'm not sure I understand the output you quoted: Is your implementation recognizing this as valid json? Are you rolling a hand-written parser/serializer or are you going with the standard go one?

I would have expected most problems to have to do with float serialization and string escape sequence parsing.

I think the fuzzer got a bit overly eager when minimizing the test cases for invalid surrogate pair escapes in strings, removing the closing quotation marks from some test cases (since my rust implementation emitted the error directly upon encountering the invalid surrogate pair). To make sure that your implementation rejects unpaired surrogates, you should probably add trailing quotes to those nay/surrogate tests that lack them. Since go is not as strict about unicode as ssb, I expect you could run into problems otherwise.