-1 we don't need any more access modifiers. We already have an excessive amount: 5 On Thu, Dec 8, 2016 at 12:55 PM Jim Malak via swift-evolution < swift-evolution@swift.org> wrote:
> Hi Tino, > This is my first use of this forum. I certainly did not mean to cause pain > for anyone. > At Gonzalo's invitation I have looked over the thread for his proposal and > I am withdrawing my request and backing his with a very heavy +1. > The group has done an amazing job with the open source development of > Swift. Though this email approach may cause some problems, all of you have > advanced the language tremendously in a very short period of time. > If I have offended anyone I ask their forgiveness. Since you mentioned it > I will state that the Xcode approach to project groups is one that I have > yet to understand the merit of. > Gonzalo: please let me know how I can assist you. > - Jim > > _____________________________ > From: Tino Heth <2...@gmx.de> > Sent: Thursday, December 8, 2016 12:08 PM > > Subject: Re: [swift-evolution] Any consideration for directoryprivate as a > compliment to fileprivate? > To: Jim Malak <jim.ma...@beryle-lee.com> > Cc: <swift-evolution@swift.org> > > > I guess it's just coincidence, but this thread about "directoryprivate" > did start while the thread about "typeprivate" (which ended up as a general > discussion) is fading away without real results… > > To me, this looks like an indication for two* things: > > a) Access levels are broken** in Swift 3 > > b) The tool used for discussion (mailing list) is broken** as well > > Right now, I'm in the mood to write a rant about b) (that might change > until I have time to do so ;-), but returning back to topic, I really don't > think adding more and more levels with more and more magic words is a bad > idea. > Additionally, "directoryprivate" will be really painful due to the way > Xcode deals with the filesystem (although that might be an argument for > adding it, as imho Xcode needs improvement in this aspect anyways ;-) > > - Tino > > * three things to be honest; but the last one would be to controversial > for a half sentence without explanation > > ** actually, I think "broken" is way to hard — but judging from past > experience, I come to the sad conclusion that provoking statements are > better to drive discussion ;-) > > _______________________________________________ > 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