JSON schema validation during object deserialization in Nim

When using the json module to restore application state, Nim lacks a native mechanism to enforce schema validation between the serialized string and internal type structures. While parseJson converts strings into JsonNodes, it does not inherently verify structural integrity or type compatibility before the manual assignment occurs.

This becomes particularly complex when dealing with deeply nested objects that rely on the ARC or ORC memory management systems. Since Nim requires manual mapping from JsonNodes to objects, malformed or unexpected data structures can lead to runtime errors or inconsistent state if the validation logic does not account for edge cases.

What are the recommended patterns for implementing strict schema validation during deserialization without incurring significant overhead? How do the --arc and --orc flags affect the safety of partially initialized objects during a failed restoration process?