[swift-evolution] [Pitch] Consistent bridging for NSErrors at the language boundary

Charles Srstka cocoadev at charlessoft.com
Wed Jun 22 04:43:16 CDT 2016

> On Jun 22, 2016, at 1:28 AM, Douglas Gregor <dgregor at apple.com> wrote:
> On Jun 20, 2016, at 11:03 AM, Charles Srstka via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> It was deferred until after Swift 3.0.
>> https://github.com/apple/swift-evolution/pull/331 <https://github.com/apple/swift-evolution/pull/331>
>> I plan to resubmit the proposal after Swift 3.0 comes out. Do you have any improvements or suggestions for it
> The core team is reconsidering the deferral, because tackling this completely is a fairly significant source-breaking change that we wouldn't want to do post-Swift 3. That said, this is a tricky feature to get right, because it involves dealing with intricacies of Swift's Objective-C interoperability as well as the inner workings of NSError. I'll have some comments on your proposal as well as my own thoughts on an implement approach in the next few days. Hang in there :)

That is great news! This proposal seems like a good fit for Swift 3.0, to my mind, as it is very much along similar lines as the NSURL -> URL, NSDate -> Date, etc. conversions that are already being made.

I look forward to hearing your comments.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160622/24ba4762/attachment.html>

More information about the swift-evolution mailing list