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

[Riley Testut]

> Apparently the proposal is not updated yet. `EncodingError` and `DecodingError` enums were said to be added as part of the move to the Standard Library.
> https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170417/036001.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170417/036001.html>
> 
> Regards,
> Anders

Ah thanks, glad to hear this!

> On Apr 25, 2017, at 6:30 PM, Anders Ha <hello at andersio.co> wrote:
> 
>> 
>> On 26 Apr 2017, at 9:11 AM, Riley Testut via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> I’m sure this has already been discussed, but why are the methods throwing NSErrors and not Enums? If I’m remembering correctly, the original reason for this was because this was meant to be a part of Foundation. Now that this is in the Standard Library, however, it seems strange that we’re still using NSError.
>> 
> 
> Apparently the proposal is not updated yet. `EncodingError` and `DecodingError` enums were said to be added as part of the move to the Standard Library.
> https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170417/036001.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170417/036001.html>
> 
> Regards,
> Anders
> 
>> Second question that again I’m sure was asked and answered already, but: why do we require implementations for each concrete numeric type (Int, Int8, Int16, Float, etc), instead of using protocols (such as the new Integer protocols)?
>> 
>>> On Apr 25, 2017, at 3:59 PM, Douglas Gregor via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> 
>>> Proposal Link: https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md <https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md>
>>> 
>>> Hello Swift Community,
>>> 
>>> The review of SE-0166 “Swift Archival & Serialization” ran from April 6...12, 2017. The proposal is accepted with some minor modifications. Specifically, the core protocols and types will be sunk down into the Swift standard library for more tight integration with the Swift language and compiler, and the operations specifically involving Foundation’s “Data” type will be removed. The proposal document has been updated with more detail. Thank you everyone for participating in this review!
>>> 
>>> 	- Doug
>>> 	Review Manager
>>> 
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> 
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170425/66447eee/attachment.html>