Skip to content

Qualify the names of extended types in module interfaces #32780

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

Closed

Conversation

beccadax
Copy link
Contributor

@beccadax beccadax commented Jul 9, 2020

This was previously done inconsistently—we did it for certain generic types, but not otherwise. Now we always do it unless -module-interface-preserve-types-as-written has been specified. Fixes SR-13050 / rdar://64947446.

This was previously done inconsistently—we did it for certain generic types, but not otherwise. Now we always do it unless `-module-interface-preserve-types-as-written` has been specified. Fixes SR-13050 / rdar://64947446.
@beccadax beccadax marked this pull request as draft July 9, 2020 05:18
@beccadax
Copy link
Contributor Author

beccadax commented Jul 9, 2020

Note that this has the potential to cause module interfaces which currently, coincidentally aren't affected by type names shadowing module names to start having trouble with it. (It did in our own test suite!) I need to evaluate the impact of this.

@swift-ci please test source compatibility

@shahmishal
Copy link
Member

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

  • How to change the base branch: (Link)
  • More detail about the branch update: (Link)

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