Am 2016-12-01 11:08, schrieb Álvaro Monteiro via swift-evolution:
> - Typeprivate would allow to abandon the odd fileprivate. Access level
> would be constrained to swift constructs (structs, classes and
> extensions) and not to a compiler artifact (file).
Files are not compiler artifacts but design artifacts.
They group related stuff which was designed together and which should be
I really like `fileprivate` and how Swift currently handles access control.
swift-evolution mailing list