<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Sending out again to the whole mailing list ;-)</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature"><div><span style="background-color: rgba(255, 255, 255, 0);">There are a lot of great changes here which make sense after the fact. I'll try to play around with them.</span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">One thing I'm concerned about: with the new Optional conformance, why do we still need decodeIfPresent and encodeIfPresent? They seem superfluous now, and potentially confusing. Should users call encodeIfPresent/decodeIfPresent or encode/decode with an optional type? Do the have the same semantics?</span></div></div><div><br>On 23 Jun 2017, at 21:47, Itai Ferber via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</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 swift-evolution,</p>
<p dir="auto">Over the course of the past few weeks, we’ve been gathering feedback about the outcome of <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md" style="color:#3983C4">SE-0166</a> and <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0167-swift-encoders.md" style="color:#3983C4">SE-0167</a> (both internally and externally), and we gathered a collection of updates that we’re going to introduce to the proposals and to the implementation.</p>
<p dir="auto">Attached is rendered HTML (I don’t want to make your mail clients unusable like last time!) that lays out what we’d like to do. We’re not looking to do a full review of these changes, but if you have feedback or questions, we’re happy to get responses here.</p>
<p dir="auto">Please note that some of these features have already been implemented (the new error types, some of the optionality changes, collection conformances, etc.), but we are receptive to comments on all of it. The existing proposals will also be updated to incorporate these updates.</p>
<p dir="auto">Thanks for all of your feedback!</p>
<p dir="auto">— Itai</p>
</div>
</div>
</div></blockquote><blockquote type="cite"><div><swift-archival-serialization-updates.html></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>