-
Notifications
You must be signed in to change notification settings - Fork 388
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
Don't attempt to clear elaborated type duplicates #1676
Merged
kimgr
merged 1 commit into
include-what-you-use:master
from
bolshakov-a:elaborated_in_multiple_decl
Jan 26, 2025
Merged
Don't attempt to clear elaborated type duplicates #1676
kimgr
merged 1 commit into
include-what-you-use:master
from
bolshakov-a:elaborated_in_multiple_decl
Jan 26, 2025
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
It was assumed in include-what-you-use#1232 that at most one elaborated type can "own" a tag declaration (i.e. none of possible following similar types redeclares that declaration), hence there should be no duplicates in fwd_decl_map. Even if that assumption is true, an ElaboratedTypeLoc may be handled more than once if it corresponds to different AST nodes. It happens when that type is used in a declaration of several variables. Elaborated types should obviously not be removed in any case because they are part of user's main code and not of #include or fwd-decl lists. This fixes include-what-you-use#1674.
Informational: IWYU dogfood resultsinclude-what-you-use (exit: 0)
fix_includes.py (exit: 0)
diff |
LGTM, thank you! |
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.
It was assumed in #1232 that at most one elaborated type can "own" a tag declaration (i.e. none of possible following similar types redeclares that declaration), hence there should be no duplicates in
fwd_decl_map
. Even if that assumption is true, anElaboratedTypeLoc
may be handled more than once if it corresponds to different AST nodes. It happens when that type is used in a declaration of several variables.Elaborated types should obviously not be removed in any case because they are part of user's main code and not of
#include
or fwd-decl lists.This fixes #1674.