-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[Sema] Remove lookupBoolType #22488
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] Remove lookupBoolType #22488
Conversation
|
||
auto tyDecl = dyn_cast<NominalTypeDecl>(results.front()); | ||
if (!tyDecl) { | ||
diagnose(SourceLoc(), diag::broken_bool); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're not going to bother diagnosing this anymore, you can remove the diagnostic too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use this diagnostic elsewhere in TypeCheckDeclObjC and with Bool.init(_builtinBooleanLiteral:)
in CSApply
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although arguably the last one could be its own diagnostic. These broken diagnostics are something I want to improve in the future however.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the 'broken stdlib' diagnostics should become fatal. Parts of the compiler don't recover well from these and assert later, so we may as well just exit early when it happens.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you suggesting something like llvm_unreachable
for these 'broken stdlib' diagnostics?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I definitely have run into cases where the failures are pretty terrible and at times you just get weird things like the literal doesn't conform to equatable or some equally odd until you look through and find special look ups in the compiler.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think for this patch I'll go ahead and add back the diagnostic, but in a follow up I'll fix up these broken diagnostics to be fatal.
d1d06ee
to
a9f3e40
Compare
diagnose broken bool fix
a9f3e40
to
e9f4217
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice cleanup
@swift-ci please smoke test |
@CodaFi Can you run CI again please? |
@swift-ci Please smoke test |
⛵️ |
No description provided.