Skip to content

[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

Merged
merged 1 commit into from
Feb 12, 2019
Merged

Conversation

Azoy
Copy link
Contributor

@Azoy Azoy commented Feb 9, 2019

No description provided.


auto tyDecl = dyn_cast<NominalTypeDecl>(results.front());
if (!tyDecl) {
diagnose(SourceLoc(), diag::broken_bool);
Copy link
Contributor

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.

Copy link
Contributor Author

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

Copy link
Contributor Author

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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?

Copy link
Member

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.

Copy link
Contributor Author

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.

@Azoy Azoy force-pushed the remove-lookupBoolType branch from d1d06ee to a9f3e40 Compare February 9, 2019 04:00
diagnose broken bool

fix
@Azoy Azoy force-pushed the remove-lookupBoolType branch from a9f3e40 to e9f4217 Compare February 9, 2019 06:13
Copy link
Contributor

@CodaFi CodaFi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice cleanup

@CodaFi
Copy link
Contributor

CodaFi commented Feb 9, 2019

@swift-ci please smoke test

@Azoy
Copy link
Contributor Author

Azoy commented Feb 12, 2019

@CodaFi Can you run CI again please?

@jrose-apple
Copy link
Contributor

@swift-ci Please smoke test

@CodaFi
Copy link
Contributor

CodaFi commented Feb 12, 2019

⛵️

@CodaFi CodaFi merged commit 4fa53c1 into swiftlang:master Feb 12, 2019
@Azoy Azoy deleted the remove-lookupBoolType branch February 13, 2019 00:03
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