Skip to content

[5.5] Do not build Swift interface files into binary modules when performing a canImport query. #39140

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
Sep 3, 2021

Conversation

artemcm
Copy link
Contributor

@artemcm artemcm commented Sep 2, 2021

Cherry-pick of #39139

Explanation: We should hold off actually building the binary module file until it is imported. canImport queries can happen, for example, during dependency scanning, when we do not wish to have the scanner tool execute any module builds.

Scope of Issue: Dependency scanning actions run during explicit module builds may unnecessarily build modules when querying if said modules can be imported, resulting in poor performance.

Risk: Low

Issue: rdar://82603098

Code Reviewed By: @nkcsgexi

Testing Details: Regression test included

…g a `canImport` query.

We should hold off actually building the binary module file until it is imported.
`canImport` queries can happen, for example, during dependency scanning, when we do not wish to have the scanner tool execute any module builds.

Resolves rdar://82603098
@artemcm artemcm added the r5.5 label Sep 2, 2021
@artemcm artemcm requested a review from nkcsgexi September 2, 2021 17:11
@artemcm artemcm requested a review from a team as a code owner September 2, 2021 17:11
@artemcm
Copy link
Contributor Author

artemcm commented Sep 2, 2021

@swift-ci please test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍒 release cherry pick Flag: Release branch cherry picks swift 5.5
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants