Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels

How about private(world), public(module), internal(file)? :-) Slava > On Mar 25, 2017, at 4:15 PM, Adrian Zubarev via swift-evolution > wrote: > > Please do not start a debate about `private(module)` which is equavalent to > `internal`, otherwise you could equally use a parametrized `public`

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

> On Mar 25, 2017, at 2:11 AM, Carl Brown1 via swift-evolution > wrote: > Yes, it would change my opinion of it. I wouldn't become a strong supporter > because I don't see any value in it, but a rigorous proof that this proposal > could not possibly introduce regressions to any existing codebas

Re: [swift-evolution] Swift null safety questions

> On Mar 23, 2017, at 9:01 AM, Joe Groff via swift-evolution > wrote: > > setjmp and longjmp do *not* work well with Swift since they need compiler > support to implement their semantics, and since Swift does not provide this > support, setjmp-ing from Swift is undefined behavior. Empirical ev

Re: [swift-evolution] Swift null safety questions

On March 25, 2017 at 9:56:03 PM, Gwynne Raskind (gwy...@darkrainfall.org) wrote: On Mar 25, 2017, at 19:27, Elijah Johnson via swift-evolution < swift-evolution@swift.org> wrote: On March 25, 2017 at 7:15:59 PM, Elijah Johnson (ejrx7...@gmail.com) wrote: On March 25, 2017 at 10:24:23 AM, El

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

> On Mar 25, 2017, at 6:46 AM, Jonathan Hull wrote: > >> On Mar 25, 2017, at 6:39 AM, Brent Royal-Gordon > > wrote: >> >>> On Mar 25, 2017, at 12:32 AM, Jonathan Hull via swift-evolution >>> mailto:swift-evolution@swift.org>> wrote: >>> >>> • Remove ‘private

Re: [swift-evolution] Swift null safety questions

> On Mar 25, 2017, at 19:27, Elijah Johnson via swift-evolution > wrote: > > > On March 25, 2017 at 7:15:59 PM, Elijah Johnson (ejrx7...@gmail.com > ) wrote: >> >> >> >> On March 25, 2017 at 10:24:23 AM, Elijah Johnson (ejrx7...@gmail.com >>

Re: [swift-evolution] [Draft] Package Manager Custom Targets Layout

Hi, I like the part of the proposal which stops inferring targets from the directory layout; I’ve always found that stuff pretty annoying. Two points: 1) I’m not sure about listing all of the test targets together with the product targets. I feel it may be better to have them as separate Array

Re: [swift-evolution] Swift null safety questions

On March 25, 2017 at 7:15:59 PM, Elijah Johnson (ejrx7...@gmail.com) wrote: On March 25, 2017 at 10:24:23 AM, Elijah Johnson (ejrx7...@gmail.com) wrote: On March 23, 2017 at 12:01:48 PM, Joe Groff (jgr...@apple.com) wrote: On Mar 22, 2017, at 7:25 PM, Elijah Johnson wrote: On March 22,

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels

Please do not start a debate about `private(module)` which is equavalent to `internal`, otherwise you could equally use a parametrized `public` for everything. public(outside_module), public(only_inside_module), public(only_in_this_file) or public(nowhere) `internal` is just fine as it is.

Re: [swift-evolution] Swift null safety questions

On March 25, 2017 at 10:24:23 AM, Elijah Johnson (ejrx7...@gmail.com) wrote: On March 23, 2017 at 12:01:48 PM, Joe Groff (jgr...@apple.com) wrote: On Mar 22, 2017, at 7:25 PM, Elijah Johnson wrote: On March 22, 2017 at 8:41:25 PM, Joe Groff (jgr...@apple.com) wrote: > On Mar 22, 2017, at

Re: [swift-evolution] [Review] SE-0160: Limiting @objc inference

> On Mar 24, 2017, at 10:09 AM, Douglas Gregor wrote: > >> I'm actually not worried about methods so much as properties. KVC is >> completely untyped on the Objective-C side, and there are several different >> mechanisms there which use KVC with poorly validated external strings, like >> bindi

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0159: Fix Private Access Levels

> On Mar 23, 2017, at 18:35, Matthew Johnson via swift-evolution > wrote: > > On Mar 23, 2017, at 8:27 PM, Drew Crawford > wrote: > >> >> The obvious example would be Rust. Rust has exactly two visibilities, and >> merely one keyword. By default, members ar

Re: [swift-evolution] [Draft] Package Manager Custom Targets Layout

I recently experienced these pain points when trying to support SwiftPM on some of our libraries. I think this proposal goes a long way to alleviate most of the those I experienced. On Fri, Mar 24, 2017 at 4:26 PM, Ankit Aggarwal via swift-evolution < swift-evolution@swift.org> wrote: > Hi, > >

Re: [swift-evolution] Swift null safety questions

On March 23, 2017 at 12:01:48 PM, Joe Groff (jgr...@apple.com) wrote: On Mar 22, 2017, at 7:25 PM, Elijah Johnson wrote: On March 22, 2017 at 8:41:25 PM, Joe Groff (jgr...@apple.com) wrote: > On Mar 22, 2017, at 4:07 PM, Elijah Johnson wrote: > > Hi, > > Note that this thread has branched of

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

I am confused. Half of my email was about how to encapsulate smaller than the entire submodule using ‘module { }' > On Mar 25, 2017, at 6:39 AM, Brent Royal-Gordon > wrote: > >> On Mar 25, 2017, at 12:32 AM, Jonathan Hull via swift-evolution >> mailto:swift-evolution@swift.org>> wrote: >> >>

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

> On Mar 25, 2017, at 12:32 AM, Jonathan Hull via swift-evolution > wrote: > > • Remove ‘private’ keyword > • Rename ‘fileprivate’ to ‘local’ with the understanding it now means > local to the containing submodule > • If no submodule is declared, the file is its own anonymous

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

• What is your evaluation of the proposal? +1 • Is the problem being addressed significant enough to warrant a change to Swift? Yes. For some strange reason, i can’t bring myself to write `fileprivate` instead of `private` by default - if i don’t specifically think of it, i end up with privat

Re: [swift-evolution] [Pitch] Localized Swift Frameworks

I have to second (third) that. Also, cosider the fact that there were very passionate debates about naming certain methods to follow Swift 3 API guidelines. Who would localize the language? Enthusiasts? Who'd approve the localization? Would we allow anyone create his own? Imagine one school te

Re: [swift-evolution] [Pitch] Localized Swift Frameworks

> On 24 Mar 2017, at 21:40, Jean-Daniel via swift-evolution > wrote: > > >> Le 24 mars 2017 à 18:28, Jeff Kelley via swift-evolution >> a écrit : >> >> One of the things that struck me from today’s Apple press release about >> Swift Playgrounds being localized in more languages is this scr

[swift-evolution] [Review] SE-0159: Fix Private Access Levels

Hi Doug (and list), > What is your evaluation of the proposal? -1 > Is the problem being addressed significant enough to warrant a change to > Swift? No, I also think it is not the _correct_ answer to the actual issues with access control in Swift right now. > Does this proposal fit well w

Re: [swift-evolution] [Draft] Package Manager Custom Targets Layout

Sounds good on a first read through. Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github: http://github.com/Balancingrock Project: http://swiftfire.nl > On 24 Mar 2017, at 21:26, Ankit Aggarwal via swift-evolution > wrote: > > Hi, > > We would love to g

Re: [swift-evolution] [Review] SE-0159: Fix Private Access Levels

Ok, I have been thinking all day if I can come up with of a design which would still provide scoped private (and keep file-based private) without causing the current confusion. Here is the best I have so far. I warn you it trades one weirdness for another, but at least the new weirdness is pro