-
Notifications
You must be signed in to change notification settings - Fork 15.1k
[clang][clang-scan-deps] Add named modules to format 'experimental-full' #145221
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
naveen-seth
merged 7 commits into
llvm:main
from
naveen-seth:dep-scanning-format-full-cxx20-module-support
Jun 24, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
981742e
[clang][clang-scan-deps] Add named modules to format 'experimental-full'
naveen-seth 08b470d
Omit 'named-module-deps: […]' when empty to avoid updating all tests
naveen-seth 1b4e90e
Avoid implicit conversion in non-empty check
naveen-seth 2cde5be
"module-name" -> "named-module"
naveen-seth 2628a65
Let consumers decide whether to handle named module scan results
naveen-seth 868934a
Fix wording mistake in comment
naveen-seth 74772e0
Make test windows-compatible
naveen-seth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Static analysis flagged code around here and I am stuck trying to understand what
ModuleNameis being used for here. Is this dead code? If not there should really be a comment explaining how it is used.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ModuleNamestores the name of the exported standard C++ module.After
takeTranslationUnitDeps(), it is stored in theTranslationUnitDeps.ID.ModuleNamefield (here).I don't think this should be dead code because it is used in
ClangScanDeps.cppwhen using the--experimental-fullformat (first reassigned here, then used for printing here).Maybe it would help improve clarity if we keep
ContextHashandModuleNametogether in aModuleIDfield withinFullDependencyConsumer, just as TranslationUnitDeps does, rather than keeping them ungrouped.This would then more directly lead to the documentation of
ModuleID.ModuleName(here).