Sending out again to the whole mailing list ;-) There are a lot of great changes here which make sense after the fact. I'll try to play around with them.
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? > On 23 Jun 2017, at 21:47, Itai Ferber via swift-evolution > <swift-evolution@swift.org> wrote: > > Hi swift-evolution, > > Over the course of the past few weeks, we’ve been gathering feedback about > the outcome of SE-0166 and SE-0167 (both internally and externally), and we > gathered a collection of updates that we’re going to introduce to the > proposals and to the implementation. > > 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. > > 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. > > Thanks for all of your feedback! > > — Itai > > <swift-archival-serialization-updates.html> > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
