Skip to content

[Sema] Downgrade to a warning public imports of an underlying private module #40770

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
Jan 10, 2022

Conversation

xymus
Copy link
Contributor

@xymus xymus commented Jan 7, 2022

Diagnostics of public imports of private modules are more likely to be wrong about imports of the underlying module from a Swift overlay due to weird project configuration/installation, or the fact that private overlays are installed in the same folder as public ones. Let's always downgrade these diagnostics to warnings to help landing the rest of the diagnostics as errors.

rdar://87262431

… module

Diagnostics of public imports of private modules are more likely to be
wrong about imports of the underlying module from a Swift overlay due to
project configuration/installation, or the fact that private overlays
are installed in the same folder as public ones. Let's always downgrade
these diagnostics to warnings to help landing the rest of the
diagnostics as errors.

rdar://87262431
@xymus
Copy link
Contributor Author

xymus commented Jan 7, 2022

@swift-ci Please smoke test

@xymus xymus requested a review from nkcsgexi January 10, 2022 17:39
@xymus xymus merged commit 3f815ac into swiftlang:main Jan 10, 2022
@xymus xymus deleted the public-overlays branch January 10, 2022 17:39
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.

1 participant