[swift-evolution] Analysis of existing scopes

Jonathan Hull jhull at gbis.com
Wed Feb 22 11:01:24 CST 2017

> For this post, my only question is - why is private allowed when, in reality, it is fileprivate for protocols?

Swift 3 private means private to the current scope. For top-level items, that scope is the file.

If we are allowed to nest protocols inside structs/classes (which I believe is happening in Swift 3.2), then we will be able to have protocols private to those types.


More information about the swift-evolution mailing list