Skip to content

Conversation

@jckarter
Copy link
Contributor

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.

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.
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter
Copy link
Contributor Author

@tkremenek I ran the full tests in order to maximize coverage. Would you be able to merge this if the tests pass?

@jckarter
Copy link
Contributor Author

@milseman swiftpm fails due to an escaping closure:

/home/buildnode/jenkins/workspace/swift-PR-Linux/swiftpm/Sources/Basic/LazyCache.swift:41:21: error: invalid conversion from non-escaping function of type '(Class) -> () -> T' to potentially escaping function type '(_) -> () -> _'
        self.body = body
                    ^~~~

@gottesmm
Copy link
Contributor

@milseman said he is going to revert the change.

@jckarter
Copy link
Contributor Author

@swift-ci smoke test

@jckarter
Copy link
Contributor Author

OS X build fails on playground support, looks related. I'll investigate.

@milseman
Copy link
Member

swiftpm should be fine now, builders are passing

@jckarter
Copy link
Contributor Author

@milseman Thanks!

@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter
Copy link
Contributor Author

Fixed the swiftpm failure. Trying again.

@jckarter
Copy link
Contributor Author

@swift-ci Please test OS X

@tkremenek tkremenek self-assigned this Jul 30, 2016
@jckarter jckarter merged commit c748ba6 into swiftlang:master Jul 30, 2016
@jckarter jckarter deleted the no-bridged-default-literal-types branch July 30, 2016 05:17
@parkera
Copy link
Contributor

parkera commented Jul 30, 2016

@jckarter what's the PR for the follow up work?

@jckarter
Copy link
Contributor Author

@parkera Haven't filed a public pr yet, but I filed 27616753 internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants