Finalize modules.json format
#3488
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
StephanTLavavej
added
enhancement
CaseyCarter
approved these changes
Feb 21, 2023
|
I will merge this into both repos when the checks complete, so that we will have a commit that exactly corresponds to 17.6p3 before we start accumulating 17.7p1 work. |
strega-nil-ms
approved these changes
Feb 21, 2023
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.
@olgaark has requested that
modules.jsonfollow a new format before VS 2022 17.6 ships. This simply lists the source files for the Standard Library Modules in an array; the build system will discover what modules they provide, and their dependency relationship. As this has not yet shipped to users for General Availablity, the version number is still specified as 1.0.