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

Douglas Gregor dgregor at apple.com
Fri Jan 29 12:23:04 CST 2016

> On Jan 28, 2016, at 11:35 PM, Fabian Ehrentraud <Fabian.Ehrentraud at willhaben.at> wrote:
> Too bad to hear the PR was rejected by the Core Team. I'm sad about it, but the reasoning sounds valid.
>> Solution #2 is asking for a warning, which is outside the scope of the Swift evolution process.
> I was a bit baffled by this information at first, but it's true that the goals of the Swift evolution process state that. I'm not sure though, how to propose additional warnings, when I only have the idea and no code to provide as a PR? The Contributing guidelines do not clarify that case. Should I just create a ticket at bugs.swift.org <http://bugs.swift.org/>?

A warning is a feature of the compiler, so filing a feature request at bugs.swift.org is appropriate. 

	- Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160129/8dc4b2f5/attachment.html>

More information about the swift-evolution mailing list