-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix the TypeChecker's omitNeedlessWords to use interface types. #7212
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 the TypeChecker's omitNeedlessWords to use interface types. #7212
Conversation
…tlang#7193) ...avoiding a crash when trying to detect near misses of protocol requirements. Unfortunately I can't come up with a test case for the VarDecl changes; everything I try seems to already work. But using interface types is more correct anyway. https://bugs.swift.org/browse/SR-3812
@swift-ci Please test |
Build failed |
|
Tagging in @bcardosolopes again. We're seeing a disturbing number of these... |
@jrose-apple first time I see this one. Is there a way to reproduce this one directly with clang? i.e., can you help me getting an easy way to reproduce? |
I have no idea. As far as I know no one sees these locally, and I don't know if they're reproducible, but over the past week or two there's been a much higher incidence rate of failures in ASTReader and ASTWriter, even for clean builds with fresh module caches. (It's possible no one sees this locally because no one does clean builds locally.) |
@jrose-apple any chance that CI can re-try/re-stress this on top of 658ce8b57dff0720013241d5d6a301e084fdbb68 instead? Finding the culprit commit (if any) in the recent changes would be a start |
Can you make (but not merge) a PR containing the reverts, and then we can test it? I don't think this PR is related, and I'd still like to get it into Swift 3.1, so we can go test there. Oh, I also remembered "please test" isn't actually a clean build by default. Maybe that's related here. |
LGTM |
@swift-ci Please test macOS |
@objc
protocol in an imported Swift module (as opposed to an imported Objective-C module or the Swift module currently being compiled).