-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Diagnostics] Removing FailureDiagnosis::visitCoerceExpr from CSDiag #29064
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
[Diagnostics] Removing FailureDiagnosis::visitCoerceExpr from CSDiag #29064
Conversation
@swift-ci please smoke test |
38f2f2e
to
a88f3fb
Compare
a88f3fb
to
4443966
Compare
@swift-ci please smoke test |
Thank you @xedin :)) |
@LucianoPAlmeida Thank you for taking care of it! |
I think this may be causing the source compat suite to fail for a few projects (https://ci.swift.org/job/swift-PR-source-compat-suite-debug/2157), looks like |
@hamishknight I'm going to revert (#29084) but I'll also open a PR to address that. We definitely can get locators without an anchor but a valid path while comparing generics... |
@xedin Sorry for the issue, let me know if I can help with that? :) |
No problem, I got it covered! |
Thank you so much 💯 |
@LucianoPAlmeida Could you please try to reduce a simple test-case from project crashes so we could include it into validation test? |
@xedin Sure 👍 |
Follow up #29011, fixing the remaining failures diagnostics and removing
FailureDiagnosis::visitCoerceExpr
fromCSDiag
.cc @xedin @hborla