[swift-evolution] [Proposal][Discussion] Modular Swift
devteam.codafi at gmail.com
Tue Feb 21 21:08:01 CST 2017
Sorry, been replying to multiple sub-threads today.
For bar(), because you wish to be able to
1) Not export it across the outermost module boundary
2) But still use it internally
Internal access is required. Any higher and you would export (violating 1), any lower and you wouldn’t be able to internally import (violating 2).
For baz(), because you wish to be able to
1) Not export it across the outermost module boundary,
2) Or even your own internal submodule boundary
Private or fileprivate suffices depending on the scoping you wish for it to have within the file/interface it’s a part of relative to the other APIs in the submodule.
> On Feb 21, 2017, at 10:04 PM, Brent Royal-Gordon <brent at architechies.com> wrote:
> I specified two different behaviors for `bar()` and `baz()`. I see now that you describe `internal` as having the behavior I want for `bar()`. Is there a way I can get the behavior I want for `baz()`?
> Brent Royal-Gordon
> Sent from my iPhone
> On Feb 21, 2017, at 6:51 PM, Robert Widmann <devteam.codafi at gmail.com> wrote:
>>> What access modifiers do I put on `bar()` and `baz()` so that `MyMod` can access `bar()` but not `baz()`, and code outside `MyMod` can access neither `bar()` nor `baz()`?
More information about the swift-evolution