On 08/25/2015 09:03 AM, Sönke Ludwig wrote: > The performance benefit comes from the fact that almost all of JSON is a > subset of ASCII, so that lexing the input will implicitly validate it as > correct UTF. The only places where actual UTF sequences can occur is in > string literals outside of escape sequences. Depending on the type of > document, that can result is a lot less conditionals compared to a full > validation of the input.
I see, then we should indeed exploit this fact and offer lexing of ubyte[]-ish ranges.