> On Jun 29, 2016, at 13:13, Jose Cheyo Jimenez <ch...@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. Jordan _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
