[swift-evolution] [Review] SE-0166: Swift Archival & Serialization

2017-04-13 Thread Johannes Lund via swift-evolution
This might be too late, but anyway: > What is your evaluation of the proposal? Unsure. For archival purposes/NSCoding replacement this seems great. As the best way to do decode JSON from external APIs I find it at least to be very unconvincing. But then, I’m not sure if this is a goal of the pro

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0166: Swift Archival & Serialization

2017-04-10 Thread Johannes Lund via swift-evolution
Hi! To begin with, I have three questions: 1. Are these proposals purely meant for archival or do they also aim to be the basis of an optimal solution for decoding/unmarshalling JSON from external APIs? 2. How are Optionals of Codable types handled? I see no mentions of this. Do they map to miss