[swift-evolution] [Discussion] A Problem With SE-0025?

Jordan Rose jordan_rose at apple.com
Wed Jun 29 15:15:47 CDT 2016

> On Jun 29, 2016, at 13:13, Jose Cheyo Jimenez <cheyo at masters3d.com> wrote:
> I know this might be have been brought up before but 
> why not just disallow the “private" keyword for top level types, extensions etc. 
> A fixit could change top level `private` to `fileprivate`. 
> I think this is a little less confusing since effectively this is what is happening in the background. 

That doesn’t fix anything for inner types, so it’s a lot less important than the rest of the amendment.

There actually is an answer to this, which is that the core team expects 'private' to be the common keyword, and therefore it’s better if you can use it at the top level and ignore ‘fileprivate’ altogether in most programs.


More information about the swift-evolution mailing list