[swift-dev] deprecating -Ounchecked

Chris Lattner clattner at nondot.org
Sat Nov 4 00:50:58 CDT 2017


> On Nov 3, 2017, at 10:23 PM, Slava Pestov via swift-dev <swift-dev at swift.org> wrote:
> 
> 
> 
>> On Nov 3, 2017, at 8:57 PM, Chris Lattner via swift-dev <swift-dev at swift.org <mailto:swift-dev at swift.org>> wrote:
>> 
>> Random question: when did you introduce -Osize, and why didn’t it go through the evolution process?  If this is a major flag that you expect users to interact with (not some obscure debugging feature) then it is part of the “UI" of Swift and seems subject to swift-evolution’s process.
> 
> Are compiler flags within the scope of the evolution process? -Osize has no effect on source compatibility or any other user-visible aspect of the language itself.

I don’t think there is an official policy, but IMO, all major new user visible features are in scope for evolution.

-Chris


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20171103/c252f5bb/attachment.html>


More information about the swift-dev mailing list