[swift-build-dev] [swift-evolution] Very limited scope for access control/(sub)modules in Swift 4

Zach Waldowski zach at waldowski.me
Mon Mar 6 12:48:34 CST 2017

I'm sort of glad to see this; was worrying that access control was
getting buried in the shuffle.

Is there anything that the community can do to help address submodules
as more of a tooling problem than a language one in the Swift 4
timeframe? Is there any low-hanging fruit to work on or proposals to
review for SwiftPM, for instance? Radars we can dupe for DevTools? That
kind of thing?

All the best —
  Zachary Waldowski
  zach at waldowski.me

On Mon, Mar 6, 2017, at 12:31 PM, Douglas Gregor via swift-evolution
> Hi all,
> Like everyone else in the Swiftverse, the core team recently spent some
> time discussing access control in Swift. While we love to see the
> enthusiasm on this topic, wholesale changes to the access control
> model—such as the introduction of submodules or a complete shift to a
> more type-centric access control model—are out of scope for Swift 4.
> The core team does feel that a small part of this discussion—the reversal
> of SE-0025’s separation of “private” and “fileprivate”---is in scope for
> Swift 4, for which there is a proposal draft here:
> 	https://github.com/apple/swift-evolution/pull/627
> 	- Doug
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-build-dev mailing list