On 30 October 2017 at 23:14, Adam Kemp <adam_k...@apple.com> wrote: > > > On Oct 30, 2017, at 4:10 PM, Mike Kluev <mike.kl...@gmail.com> wrote: > > > > "classprivate" helps to resolve this problem. if it is marked so > developer will at least think twice before making an extension to use it > > Why would they think twice, though? You’ve told them extensions can use > it, and they’ve written an extension to use it. What did they do wrong? I > don’t think the rules are nearly as clear as for protected. >
this is obvious: when they are writing a method in their own class and try to call: some.foo() it will give them and access level error (or even before that the autocomplete will not work as an early hint), they will reveal foo's definition, see "classprivate" in there and at that very point take a pause, think and make a conscious decision whether they really want it or not. if they really want it they will make an extension (which would be a legitimate use of it) if they don't need it really - they will find another way without making an extension. the (reasonable) expectation is that such a "classprivate" will reduce the number of instances where "foo" is used thus reducing the "working set" of instances i have to review when making a change to it. Mike
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
