Skip to content

Remove emitSwiftModuleSeparately option #6779

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
Aug 7, 2023

Conversation

neonichu
Copy link
Contributor

@neonichu neonichu commented Aug 4, 2023

This option has always been off by default and there are no particular tests for it, so I think we should just remove it since it makes maintaining SwiftTargetBuildDescription unnecessarily difficult. From what I can gather, this was supposed to be an optimization for build times that maybe was supposed to be tested, but it ended up never being enabled.

This option has always been off by default and there are no particular tests for it, so I think we should just remove it since it makes maintaining `SwiftTargetBuildDescription` unnecessarily difficult. From what I can gather, this was supposed to be an optimization for build times that maybe was supposed to be tested, but it ended up never being enabled.
@neonichu neonichu requested a review from abertelrud as a code owner August 4, 2023 20:44
@neonichu neonichu self-assigned this Aug 4, 2023
@neonichu
Copy link
Contributor Author

neonichu commented Aug 4, 2023

@swift-ci please smoke test

@neonichu
Copy link
Contributor Author

neonichu commented Aug 4, 2023

This will also resolve #4549 and #6577

@neonichu
Copy link
Contributor Author

neonichu commented Aug 4, 2023

I'm also pretty sure this option hasn't fully worked in a while, there are all these odds differences between this mode and the "regular" one when looking at SwiftTargetBuildDescription.

@tomerd
Copy link
Contributor

tomerd commented Aug 4, 2023

seems reasonable. can git history tell us when/who added it originally? maybe worth checking in and confirming the assumptions

@neonichu
Copy link
Contributor Author

neonichu commented Aug 4, 2023

seems reasonable. can git history tell us when/who added it originally? maybe worth checking in and confirming the assumptions

Yes, it was added in #2391

Copy link
Contributor

@MaxDesiatov MaxDesiatov left a comment

Choose a reason for hiding this comment

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

-185+0 LoC diff, nice 👍

@neonichu
Copy link
Contributor Author

neonichu commented Aug 5, 2023

For reference, I spoke to Doug and the conclusion was that not only this but also the current default mode should eventually go away and we should use the integrated driver. The refactoring that this is a part of should help us to eventually get there.

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