-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix the TypeChecker's omitNeedlessWords to use interface types. #7193
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
...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
f0038a6
to
0127ded
Compare
@swift-ci Please smoke test |
Thanks. I have a fix for a similar problem in SILGen coming up. I started ripping out VarDecl::getType altogether, to avoid this type of breakage in the future. |
@kubamracek, what's up with the TSan test failure? |
|
Flaky test, I guess. By looking at test/Sanitizers/tsan.swift, I think we need to pthread_join the two threads, or the main thread can exit before one the new threads ever gets a chance to run. Which is what I guess happened here. |
I'll submit a PR to fix that. |
@swift-ci Please smoke test |
Would still like a quick glance from Doug, but going ahead based on Slava's review. |
LGTM, sorry for the delay |
…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
...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.
SR-3812