> 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.

Thanks,
Jon
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to