[swift-evolution] Type-based ‘private’ access within a file

[BJ Homer]

The proposed relaxation to 'private' is indeed small, and it makes Swift 3's "private" a more acceptable "soft default" for restricted access, but it also removes the ability of Swift to define a truly scoped access control, which some developers have found highly useful.

I would prefer accepting this proposal over doing nothing, as I think "private" is broken right now as a soft default, which is unfortunate for a language that will be used by so many new programmers. But I think renaming access controls without a large migration, as I suggested earlier, would be better. 

-BJ

> On Apr 4, 2017, at 12:45 AM, Goffredo Marocchi via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Considering how small this private rule relaxation is, it seems strange to swat away this proposal...