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

Fabian Ehrentraud Fabian.Ehrentraud at willhaben.at
Fri Dec 11 11:00:54 CST 2015

I've added the according section. Can you think of any more pros/cons?

I'll happily accept sensible pull requests on my proposal draft at https://github.com/fabb/swift-evolution/blob/import_as_optional_by_default/proposals/0008-import-as-optional-by-default.md

> Am 10.12.2015 um 22:11 schrieb Guillaume Lessard <glessard at tffenterprises.com>:
>> 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