On Fri, Apr 21, 2017, at 11:26 AM, Tony Parker via swift-evolution wrote:> One more thing, which we realized after I sent my original email: the > default implementation of many of the protocols needs to throw errors. > Therefore we will add enum EncodingError and enum DecodingError to the > list of new types. Those enums will have various associated values > according to what is useful debug information. To preserve the ability > for developers to present these errors to users with localized and user- > presentable messages, when these enums are cast to NSError (e as? > NSError), they will have the Cocoa error domain and a Foundation- > provided code. (This is done via an extension to the enum in > Foundation). This is the best possible outcome for layering. Thanks to everyone involved for reconsidering that. Sincerely, Zachary Waldowski [email protected]
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
