-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Assume it's okay for decls in a cross-module extension to be public #18741
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
...even if the base decl isn't. This isn't normally possible, but it can come up when an imported type is import-as-member'd onto an internal Swift declaration. This isn't even such an unreasonable thing to do, since internal Swift declarations are exposed in the generated header for an app. rdar://problem/43312660
@swift-ci Please test |
@swift-ci Please test source compatibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh. Wow. LGTM
Build failed |
|
@swift-ci Please test Linux |
Okay, this is running more slowly than I expected, so @swift-ci Please test compiler performance |
Build failed |
@swift-ci Please test Linux |
...even if the base decl isn't.
This isn't normally possible, but it can come up when an imported type is import-as-member'd onto an internal Swift declaration. This isn't even such an unreasonable thing to do, since internal Swift declarations are exposed in the generated header for an app.
rdar://problem/43312660