> On Oct 7, 2016, at 3:05 PM, Zach Waldowski via swift-evolution
> <[email protected]> wrote:
>
> I third this sentiment. fileprivate is a nice idea and very clearly has its
> uses (which is why the proposal got traction in the first place), but when
> combined with the other access levels, the language feature as a whole feels
> arbitrary. In practical use, files that I felt were nicely encapsulated and
> hiding implementation details are now a scattered mix of access levels,
> adding cognitive load and making the code look unorganized for having the
> gall to use extensions to split up functionality.
>
> Sincerely,
> Zachary Waldowski
> [email protected] <mailto:[email protected]>
Beyond the textual change of using a different modifier name, I don’t see how
the encapsulation and organization of code could be affected. Really, there’s
not much point in rehashing prior discussion of SE-0025 unless there’s a
previously unconsidered angle.
Preston
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
