[swift-evolution] classprivate protection level?
adam.kemp at apple.com
Mon Oct 30 21:29:22 CDT 2017
> On Oct 30, 2017, at 5:36 PM, Noah Desch <deschnl at icloud.com> wrote:
> If I’m concerned with how much work I’ll have to do, no that’s not the key. The key is how many files do I have to read myself (only those containing a subclass or extension of my base class).
Why would you read any file before searching for usages and figuring out which files use that API? And the scope of that search is defined by the access level.
> You seem to be conflating a near instantaneous search in an IDE
No, grep would be sufficient as well. The issue is still which files to grep in the first place. Everything else comes after that. If you manually read files looking for usages of an API you’re changing then I feel sorry for you. You’re doing things the hard way.
> There doesn’t need to be anything in the language, I just need to have a defined coding convention that contributors follow. As someone else said upthread you have to be able to trust your fellow developers.
If you trust your fellow developers then you don’t need a new access scope. Use internal or public.
I’m not going to go back and forth on this any longer. We’re going in circles. We just don’t agree, and this doesn’t appear to be going anywhere.
More information about the swift-evolution