In another thread (no link because we’re not on a forum ;-) the idea was raised that in the future, if and when Swift starts using submodules, the “fileprivate” scope could be turned into “submodule” scope.
By default every file would constitute its own submodule, and developers could choose to put several files together into a submodule if they wish. Perhaps there may be a shorter word that nicely implies “submodule scope”. Nevin On Tue, Sep 27, 2016 at 12:20 PM, Jeremy Pereira via swift-evolution < [email protected]> wrote: > > > On 27 Sep 2016, at 14:20, Zach Waldowski via swift-evolution < > [email protected]> wrote: > > > > > > > > > > On Tue, Sep 27, 2016, at 01:34 AM, Jeremy Pereira via swift-evolution > > wrote: > >> As for dropping file private, why? You don’t have to use it if you don’t > >> want to, so it’s not hurting you. On the other hand, I can use it when I > >> deem it to be the right thing to do. > > > > I'll politely disagree and point out you *must* use fileprivate in order > > to get what it provides. It's unavoidable in that sense. > > That’s not the point I was making. It was mooted that fileprivate should > be dropped altogether leading to not having any means of specifying file > scope at all. I was simply pointing out that people who don’t like file > scope already have the option of not using fileprivate. > > > _______________________________________________ > 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
