Separate cxx and ixx languages #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR separates C++ module implementation and C++ module interfaces as two different languages.
This is a weird thing to do, just as it is already done to the "cpp" preprocessor language.
We are exploring the following effect: the practical difference in compiling C++ normal sources and module implementation sources and C++ module interfaces.
By having explicit C++ module interface source sets, we can compile C++ normal or module implementation sources with not concern for module dependency and ordering, and we may be certain that we must resolve module dependency and ordering for C++ module interface source sets.