Skip to content

Downgrade the TypeSystemSwiftTypeRef string validation errors #1331

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 2 commits into from
Jun 12, 2020

Conversation

adrian-prantl
Copy link

to warnings. The remaining divergences are mostly cosmetic in nature
and costly to fix. For testing purposes the code can be compiled with
-DSTRICT_VALIDATION to retain the old behavior.

When the always-qualify mode is turned off,
TyperPrinter::shouldPrintFullyQualified() insists on never printing
qualifiers for types that come from Clang modules, but the way this is
implemented this rule also fires for types from SDK overlays, which
are technically Swift modules.

Because of this the TypeSystemSwiftTyperef variant occasionally emits
more-qualified names than the SwiftASTContext variant. Fixing this is
so complex that it isn't worth the effort. It would be better to
generally switch to a representation where all non-local types are
always qualified.

rdar://problem/63700540
to warnings. The remaining divergences are mostly cosmetic in nature
and costly to fix. For testing purposes the code can be compiled with
-DSTRICT_VALIDATION to retain the old behavior.
@adrian-prantl
Copy link
Author

@swift-ci test

Copy link

@medismailben medismailben left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @adrian-prantl!

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.

2 participants