Skip to content

[6.0] Don’t reload package manifest when a header is added #7692

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

MaxDesiatov
Copy link
Contributor

@MaxDesiatov MaxDesiatov commented Jun 20, 2024

Cherry-pick of #7691.

Explanation: Currently, any new header file causes a package reload. This means that while background indexing is writing header files into the index build directory, the package will get reloaded, which is unnecessary.
Scope: isolated to known clients using this function, primarily SourceKit-LSP
Risk: low, the function itself is not used in SwiftPM
Testing: added a new unit test
Issue: rdar://128573306
Reviewer: @ahoppen @bnbarham

Currently, any new header file causes a package reload. This means that while background indexing is writing header files into the index build directory, the package will get reloaded, which is unnecessary.

(cherry picked from commit 1d0e412)
(cherry picked from commit a6da9d0)
@MaxDesiatov MaxDesiatov added bug performance Performance optimizations and improvements swift 6.0 Related to Swift 6.0 release branch labels Jun 20, 2024
@MaxDesiatov MaxDesiatov requested a review from a team as a code owner June 20, 2024 21:54
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov MaxDesiatov added the workspace Package workspace support label Jun 20, 2024
@MaxDesiatov MaxDesiatov deleted the maxd/exclude-headers-from-reloading-6.0 branch June 24, 2024 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug performance Performance optimizations and improvements swift 6.0 Related to Swift 6.0 release branch workspace Package workspace support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants