-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update for SE-0025 ('private' and 'fileprivate') #445
Conversation
Looks good to me, I wonder if we should actually consider some of these for |
Good to merge as soon as the binary drops of the toolchain have this feature |
Both |
Today's toolchain should have 'fileprivate' support (treating it largely the same as 'private'). Okay to merge? |
@swift-ci please test |
CI is in an awful state; let's make sure we are not making things worse. |
Good call. Looks like it passed—good to go? |
Similar to the work in swiftlang/swift-corelibs-foundation#445. Groundwork for SE-0025 ('private' and 'fileprivate'). No intended functionality change.
Similar to the work in swiftlang/swift-corelibs-foundation#445. Groundwork for SE-0025 ('private' and 'fileprivate'). No intended functionality change.
Similar to the work in #445. Groundwork for SE-0025 ('private' and 'fileprivate'). No intended functionality change.
Similar to the work in #445. Groundwork for SE-0025 ('private' and 'fileprivate'). No intended functionality change.
SE-0025 makes
private
restrict access to a lexical scope; the Swift 2 behavior is now namedfileprivate
. At the time of this pull request, the compiler treats bothprivate
andfileprivate
as havingfileprivate
semantics, but that will soon change.Supersedes #413; the latest amendment to SE-0025 permits some accesses that the original model (or at least our interpretation of it) would have forbidden. This was done by hand, so it's possible I missed a few cases, but it's at least a smaller diff.