[swift-evolution] classprivate protection level?
mike.kluev at gmail.com
Sun Oct 29 22:40:32 CDT 2017
On 30 October 2017 at 02:54, Adam Kemp <adam.kemp at apple.com> wrote:
> That was my original point. This is what internal does. We don’t need any
> new access levels for extensions. Internal solves these use cases. Code in
> the same module can be maintained in lockstep so you can make things
> internal as needed for extensions. Anything beyond that is effectively
> indistinguishable from public so just call it that.
if I have N big classes, each split across M files to keep size
manageable, do I need to have N different modules if i want to achieve a
good separation between classes? (same level of protection that private
gives for a class that fits in a single file) i.e. one module per one class?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution