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

Fabian Ehrentraud Fabian.Ehrentraud at willhaben.at
Thu Dec 10 15:29:13 CST 2015

Ok, I'll add this.

Impulse for this proposal was in fact the gradual transition of a project to Swift, so the newer Swift code of an app accessing the older Objective-C code of the same app. That's where this feature would shine and help a lot in the transition phase. But I guess it would not make sense to have different importing behavior for Cocoa.

> On 10.12.2015, at 22:11, Guillaume Lessard <glessard at tffenterprises.com> 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.
> Cheers,
> Guillaume Lessard

More information about the swift-evolution mailing list