Skip to content

Add diagnostics to use module aliasing when duplicate targets found #5606

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
Jun 19, 2022

Conversation

elsh
Copy link
Contributor

@elsh elsh commented Jun 18, 2022

Resolves rdar://93218209

@elsh
Copy link
Contributor Author

elsh commented Jun 18, 2022

@swift-ci smoke test

@elsh
Copy link
Contributor Author

elsh commented Jun 18, 2022

@swift-ci smoke test

@elsh elsh merged commit 33e05c7 into main Jun 19, 2022
@elsh elsh deleted the es-dupdiag branch June 19, 2022 01:56
neonichu added a commit that referenced this pull request Sep 30, 2023
… found (#5606)"

This reverts commit 33e05c7.

We should not make this suggestion without better contextual awareness because it can often be confusing, e.g. when someone is already using a module alias in a case where it isn't supposed to work (see #6841).

If we could find a way to confidently make the suggestion, we could bring it back, but currently it can be more confusing than not.
neonichu added a commit that referenced this pull request Oct 2, 2023
… found (#5606)" (#6961)

This reverts commit 33e05c7.

We should not make this suggestion without better contextual awareness because it can often be confusing, e.g. when someone is already using a module alias in a case where it isn't supposed to work (see #6841).

If we could find a way to confidently make the suggestion, we could bring it back, but currently it can be more confusing than not.
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