[swift-evolution] [Proposal] Foundation Swift Archival & Serialization

Oliver Jones oliver at deeperdesign.com
Thu Mar 23 16:28:47 CDT 2017

Fantastic. Great to hear. I look forward to reading the revised proposal!


> On 24 Mar 2017, at 3:34 am, Itai Ferber <iferber at apple.com> wrote:
> Hi Oliver,
> Thanks for your comments! We thought about this and we agree overall — we will incorporate this suggestion along with others in the next batch update as long as nothing prohibitive comes up.
> — Itai
> On 23 Mar 2017, at 7:49, Oliver Jones wrote:
> Like everyone I’m excited by this new proposal.  But…
> > protocol Codable: Adopted by types to opt into archival. Conformance may be automatically derived in cases where all properties are also Codable.
> … can I make one suggestion.  Please do not repeat the mistakes of NSCoding in combining the encoding and decoding into a single protocol.  Just as there are Encoder and Decoder classes their should be Encodable and Decodable protocols (maybe have an aggregate Codable protocol for convenience but do not force it).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170324/a5cd6a00/attachment.html>

More information about the swift-evolution mailing list