> On 7 Apr 2017, at 07:57, Charlie Monroe via swift-evolution > <swift-evolution@swift.org> wrote: > > -1 for reasons I've previously expressed in the discussions: > > - It encourages everything to be stuffed in one file. > - It doesn't actually solve anything as the new private is very close to > fileprivate, while abolishing private as truly scoped - which is a tool I use > on regular basis. > > Simply as long as it's file-based, it's not a solution, it's just another > attempt to satisfy some part of the community. I'm not saying that the > current access levels are perfect, but I still believe the way to go is to > either use submodules, and/or introducing the concept of "protected" members.
+1 to the proposal. How will submodules discourage stuffing everything into one file? I can only think of creating a submodule per each class which doesn't look like a good solution. I think this proposal is a step in the right direction. 'private' becomes type-based and the only thing left to do is extending it to extensions in the module in the future. Andrey >> On Apr 7, 2017, at 1:10 AM, Douglas Gregor via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> Hello Swift community, >> >> The review of SE-0169 "Improve Interaction Between private Declarations and >> Extensions" begins now and runs through April 11, 2017. The proposal is >> available here: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md> >> Reviews are an important part of the Swift evolution process. All reviews >> should be sent to the swift-evolution mailing list at >> >> https://lists.swift.org/mailman/listinfo/swift-evolution >> <https://lists.swift.org/mailman/listinfo/swift-evolution> >> or, if you would like to keep your feedback private, directly to the review >> manager. When replying, please try to keep the proposal link at the top of >> the message: >> >> Proposal link: >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md >> >> <https://github.com/apple/swift-evolution/blob/master/proposals/0169-improve-interaction-between-private-declarations-and-extensions.md> >> Reply text >> Other replies >> >> <https://github.com/apple/swift-evolution/blob/master/process.md#what-goes-into-a-review-1>What >> goes into a review? >> >> The goal of the review process is to improve the proposal under review >> through constructive criticism and, eventually, determine the direction of >> Swift. When writing your review, here are some questions you might want to >> answer in your review: >> >> What is your evaluation of the proposal? >> Is the problem being addressed significant enough to warrant a change to >> Swift? >> Does this proposal fit well with the feel and direction of Swift? >> If you have used other languages or libraries with a similar feature, how do >> you feel that this proposal compares to those? >> How much effort did you put into your review? A glance, a quick reading, or >> an in-depth study? >> More information about the Swift evolution process is available at >> >> https://github.com/apple/swift-evolution/blob/master/process.md >> <https://github.com/apple/swift-evolution/blob/master/process.md> >> Thank you, >> >> -Doug >> >> Review Manager >> >> _______________________________________________ >> swift-evolution mailing list >> swift-evolution@swift.org <mailto:swift-evolution@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
