Swift Unwrapped

Access Control Roller Coaster First came the private/fileprivate change (SE-0025): https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md Then came open (SE-0117): https://github.com/apple/swift-evolution/blob/master/proposals/0117-non-public-subclassable-by-default.md For the last few weeks, a faction in the community has been proposing undoing it (SE-0159): https://github.com/apple/swift-evolution/blob/master/proposals/0159-fix-private-access-levels.md Wow. Such email. Very list. https://twitter.com/swiftlybrief/status/846938309666492417 Rejection email: https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000337.html Doug Gregor opens discussion for expanding private: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170403/034903.html David Hart, with a new proposal from Doug’s suggestions: https://github.com/apple/swift-evolution/pull/668 http://www.jessesquires.com/thoughts-on-swift-access-control/ Modules Features shouldn't be des