<div dir="ltr"><div>What does the Archival & Serialization SE-0166 mean by:<br></div><div><div><br>> Some libraries, like SwiftyJSON, do this [interface between JSON and Swift] at the cost of type safety; others, like ObjectMapper and Argo below, maintain type safety by offering archival functionality for JSON types (<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md#jsonserialization-friction-and-third-party-solutions-motivation">https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md#jsonserialization-friction-and-third-party-solutions-motivation</a>)<br><br></div><div>I missed the review period (mea culpa), but I'd like to understand where the authors are coming from here.<br><br>My first questions were:<br><br>- How is SwiftyJSON type-unsafe?<br>- How does "offering archival functionality for JSON types" as in Argo or ObjectMapper recover type-safety?<br><br>On further thought, I don't think type-un/safety is what's at play here, but I'm having trouble
working out what was meant by that so I can rephrase in my own terms. Perhaps one of the authors can elaborate?<br><br></div><div>Thanks!<br></div><div><div><div><div><div><div><div class="gmail_signature">--<br>Jeremy W. Sherman<br><a href="https://jeremywsherman.com/" target="_blank">https://jeremywsherman.com/</a></div></div>
</div></div></div></div></div></div></div>