<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Fantastic. Great to hear. I look forward to reading the revised proposal!</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Regards</div><div><br>On 24 Mar 2017, at 3:34 am, Itai Ferber <<a href="mailto:iferber@apple.com">iferber@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<div style="font-family:sans-serif"><div style="white-space:normal"><p dir="auto">Hi Oliver,</p>
<p dir="auto">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.</p>
<p dir="auto">— Itai</p>
<p dir="auto">On 23 Mar 2017, at 7:49, Oliver Jones wrote:</p>
</div>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div id="2FCFFDCA-DB67-47D2-9F98-89AB144F8866"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Like everyone I’m excited by this new proposal. But…</div><div class=""><br class=""></div><div class="">> protocol Codable: Adopted by types to opt into archival. Conformance may be automatically derived in cases where all properties are also Codable.<br class=""><div class=""><br class=""></div><div class="">… 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).</div></div></div></div></blockquote>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote></div>
</div>
</div></blockquote></body></html>