JsonRazor 1.3.1

1.3.1:

Changes to existing code:

• JsonStream.StreamConverted<T>() generic class constraint was removed. Structs may now be used.
• JsonArray value indexer will now throw ArgumentOutOfRangeException when index is greater or equal to value count.
• JsonToken.GetFromPath() path first char that is type of token is now optional (but still correct to maintain compatibility) - with one exception - when path starts with array and immediately refers to next array, it can't be ommited. Example: [[{someProp

Fixes:

• Deserializer wouldn't detect private constructors.
• It probably hadn't been mentioned, but sinse 1.3.0 serialization of system types got more attention. Namely, KeyValuePair<TKey, TValue> and ValueTuple<T...> were proved to work. Sadly, Tuple<T...> class won't work, since it doesn't have default constructor and fields are readonly. If it wasn't the case, it most likely would. Structs have only constraint of fields being readonly.
• Fixed rare error that could emerge when parsing via JsonStream.
• Fixed another error that would make IToken corrupted. That would cause it to act as if arrays vanished (at least that was observed). There was also a possibility of exception being thrown when deserializing.
• Fixed rare error that could make JsonArray lose or omit first value in certain scenario (mainly when it was null).
• Fixed error with JsonArray.GetFromPath, when it received path that doesn't end with property.

New features:

• I call it 'undefined type'. Let's say, You've got to store few possible classes in one place (object property, maybe array). But they differ in definition, so there's no base class or common field/prop surface is too small. It could be worked around by putting different prop types in object, and then check for presence of right one. But now comes a second solution. When field/property is of object type, a JsonObject or JsonArray that was parsed is put inside, so You may use it to selectively perform deserialization or data querying on it. List<object> or object[] could also be used as entrance type. When parsing happens with ITokens, still JsonTokens are put inside. Also serializer will use runtime type of object that's inside object field/prop.

Performance:

JsonStream caching strategy also got more attention. Investigation revelead that number of allocations could be reduced even further. In simple test scenario allocations of internal structure went from ~40 to 4. Also size of allocated memory was reduced and usage of structures was improved. In general, I'd expect JsonStream methods to consume less memory. It's hard to tell how this translates to speed, but lowering pressure on GC is also worth. Also some code paths have been marginally improved and old code was cleaned.