Skip to content

[Index] Scope the setting of IgnoreAdjacentModules #72275

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
Mar 18, 2024

Conversation

hamishknight
Copy link
Contributor

I don't think this currently causes any issues, but make sure we unset IgnoreAdjacentModules when done loading the module.

I don't _think_ this currently causes any issues,
but make sure we unset `IgnoreAdjacentModules` when
done loading the module.
@hamishknight
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@xymus xymus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we expect to keep loading modules after this step, reverting that setting may not have the full expected impact. With the current logic we force reloading modules from swiftinterfaces by ignoring the cache, but I believe these modules once loaded still get cached. I would expect them to end up overriding the loaded adjacent swiftmodules. So subsequent module loading may pick the module built from swiftinterface even with setIgnoreAdjacentModules = false. That should be safe, in theory at least, and I don't think we load anything after this step so I'm fine with this change.

@hamishknight hamishknight merged commit 53072e8 into swiftlang:main Mar 18, 2024
@hamishknight hamishknight deleted the unset branch March 18, 2024 16:45
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.

3 participants