> On Mar 14, 2016, at 8:57 PM, Erica Sadun via swift-evolution > <[email protected]> wrote: > > >> On Mar 14, 2016, at 7:50 PM, Joe Groff via swift-evolution >> <[email protected]> wrote: >> >> >>> On Mar 14, 2016, at 6:47 PM, Ilya Belenkiy via swift-evolution >>> <[email protected]> wrote: >>> >>> I really like James's idea: >>> >>> private symbol visible within the current declaration >>> (class, extension, etc). >>> private(module) symbol visible within the current module. >>> private(file) symbol visible within the current file. >>> >>> this is very precise and crystal clear. All other already suggested names >>> have room for interpretation. These are obvious at a glance. >> >> I like this too. It also admits groupings between 'file' and 'module' in the >> future ('directory' or 'submodule' maybe), the lack of which has been often >> cited as another weakness in our current model. >> > > +1 here too. > > * It resolves my issues with public/internal vs public/private. > * As Ilya put it: "obvious at a glance" > * Uses one concept applied to different scopes. >
Tentative +1 here as well, but I think we should continue the bikeshed. I’m not yet certain this is the best we can come up with... > -- E > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
