On Apr 3, 2017, at 2:36 PM, Charles Srstka via swift-evolution <[email protected]> wrote: > >> On Apr 3, 2017, at 2:28 PM, David Hart via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> Btw, I know what I'm going to propose is a bit crazy, but how about making >> private visible to extensions even outside the file but in the same module? > > That’s actually what I suggested in my original post on the topic. My feeling > was that it would allow breaking a particularly large type into separate > files, thus alleviating the “huge file” problem that Swift has (and which > Charlie Monroe brought up as a concern). > > It’s still what I’d prefer personally, although I can understand why the core > team might want to restrict it to files.
FWIW, I think this is the way to go. It’s also more in line with other languages and how they handle “class internal”. The only one that should care about the file is fileprivate, and I honestly think I’d never wind up using that if private were fixed properly (current type + same-module extensions + any file). — Adam
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
