-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix more InternalImportsByDefault
errors
#7905
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
Fix more InternalImportsByDefault
errors
#7905
Conversation
This is a follow on to #7895. |
4de982a
to
b557c3a
Compare
@swift-ci test windows |
IIRC |
I see, I wonder if that is due to |
With the upcoming feature `InternalImportsByDefault` enabled, some versions of the Swift compiler diagnose this pattern: ``` import protocol _Concurrency.Actor // error: package protocol cannot refine an internal protocol package protocol Proto: Actor { // ... } ``` Address these diagnostics by using correct access levels for direct imports of `_Concurrency`.
b557c3a
to
c3b39cf
Compare
@swift-ci please test |
Yeah, the flag seems to be intentional:
Maybe that dates from the days before |
Can probably remove. It is indeed from before _Concurrency was always available. I recently removed it from the manifest build themselves, I just missed that bootstrap was also doing it. |
@swift-ci please test Windows |
SwiftPM doesn't build with all toolchains when the
InternalImportsByDefault
upcoming feature is properly enabled.Motivation:
With the upcoming feature
InternalImportsByDefault
enabled, some versions of the Swift compiler diagnose this pattern:Modifications:
Address these diagnostics by using correct access levels for direct imports of
_Concurrency
.Result:
SwiftPM builds with all relevant Swift compilers with
InternalImportsByDefault
enabled.