-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Sema: Don't try bridged classes as default literal types. #3870
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
Sema: Don't try bridged classes as default literal types. #3870
Conversation
One last bit of SE-0072. We shouldn't fall back to bridged classes in the absence of type context for literals anymore. By itself, this kind of hoses the use of literals with NS types, but I think we can get most of the QoI back with overlay changes I plan to propose following this.
|
@swift-ci Please test |
|
@tkremenek I ran the full tests in order to maximize coverage. Would you be able to merge this if the tests pass? |
|
@milseman swiftpm fails due to an escaping closure: |
|
@milseman said he is going to revert the change. |
|
@swift-ci smoke test |
|
OS X build fails on playground support, looks related. I'll investigate. |
|
swiftpm should be fine now, builders are passing |
|
@milseman Thanks! |
|
@swift-ci Please test |
|
Fixed the swiftpm failure. Trying again. |
|
@swift-ci Please test OS X |
|
@jckarter what's the PR for the follow up work? |
|
@parkera Haven't filed a public pr yet, but I filed 27616753 internally. |
One last bit of SE-0072. We shouldn't fall back to bridged classes in the absence of type context for literals anymore. By itself, this kind of hoses the use of literals with NS types, but I think we can get most of the QoI back with overlay changes I plan to propose following this.