Should there be any "validation" on the unicode escape characters in the JSONParser?

[hitsvilleusa]

I tried the following string in both Apple's parser and the JSONParser here "A\u0000B".

Apple's gives back the string: "AB"
BNR's gives back the string: "A"

Not sure which is right. Not sure if there is any security vulnerability with illegal unicode characters.

Simply wanted to document the difference.

[zwaldowski]

In this case, \u0000 is actually the null byte. Our use of String.withCString is causing this, and would naturally be mitigated if we even moved to a different method.

Other Unicode validation might be out-of-scope; however, the stdlib's public Unicode handling types do perform such validation.

[zwaldowski]

Loosely linked to #142 and all "not using withCString" issues.

[zwaldowski]

As such, punting from the 2.1 milestone. I don't trust building a new string parser right now; numbers is enough for one release.

[zwaldowski]

Closing due to inactivity and the general state of the repo.