[swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes

Douglas Gregor dgregor at apple.com
Thu Dec 10 16:09:29 CST 2015

> On Dec 10, 2015, at 1:11 PM, Guillaume Lessard via swift-evolution <swift-evolution at swift.org> wrote:
>> On 10 déc. 2015, at 12:52, Fabian Ehrentraud <Fabian.Ehrentraud at willhaben.at> wrote:
>> Guillaume, could you elaborate on "discussing the status quo as an alternative", it sounds good, but I'm not sure I completely got what you mean :-)
> I mean that the ‘alternatives’ section should explicitly compare the merits of leaving things as-is as compared to going ahead with the proposal. For 3rd-party libraries with limited API, importing unannotated functions as optional sounds good. However, with large frameworks (obviously including Cocoa), I think the community needs to be convinced that it will be an improvement.

Right. If we accepted this proposal, how many additional force-unwrap operations would it take in a typical iOS or OS X application that “worked” in Swift 2 to compile again in Swift 3? Are you proposing to automatically migrate Swift 2 code to Swift 3 code by adding in those force-unwrap operations, or are you asking people to rethink and reimplement the code that breaks?

	- Doug

More information about the swift-evolution mailing list