[swift-dev] deprecating -Ounchecked

Daniel Dunbar daniel_dunbar at apple.com
Thu Nov 2 12:53:44 CDT 2017


I am +1 in general, but I do feel there is a legitimate need for this for a very very small subset of code. It would feel unfortunate to need to drop to C for that — would an equivalent attribute be an alternative?

 - Daniel

> On Nov 2, 2017, at 9:52 AM, Erik Eckstein via swift-dev <swift-dev at swift.org> wrote:
> 
> Hi,
> 
> I’d like to propose to deprecate the -Ounchecked swift optimization mode.
> 
> The -Ounchecked mode actually contradicts one of the main goals of swift: to be a safe language.
> In the past we didn’t see lot of significant performance differences compared to -O (there were some improvements but also some regressions).
> Also, we want to reduce the effort of maintaining too many different optimization modes, especially because we recently added -Osize.
> 
> Deprecating would mean that we map -Ounchecked to -O.
> 
> If you have any comments or concerns, please let me know
> 
> Thanks,
> Erik
> 
> 
> 
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev



More information about the swift-dev mailing list