-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Sema] Minimum access for override
method is fileprivate
#4404
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
Conversation
@swift-ci Please test |
Build failed |
https://ci.swift.org/job/swift-PR-Linux/3523/
|
This is certainly an incremental improvement (once the Foundation change goes in), but really it should probably be switched over to access scopes like #4176. Otherwise we'll do the wrong thing for members that are more public than the enclosing type. |
Do you think it makes sense to land this or to go all the way to access scopes? |
@jrose-apple |
What's in this pull request?
CC: @jrose-apple
As discussed in #4348 (comment)
Minimum access level of
override
member inprivate
classes should befileprivate
.This
C.init()
andC.foo()
is illegal now.Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
A smoke test on macOS does the following:
device standard libraries are not built.
version of these tests are not run.
A smoke test on Linux does the following:
tests are not run.
Validation Testing
Lint Testing
Note: Only members of the Apple organization can trigger swift-ci.