-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[Clang] Check explicit object parameter for defaulted operators properly #100419
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
Endilll
merged 7 commits into
llvm:main
from
MitalAshok:explicit-obj-param-defaulted-relational
Aug 15, 2024
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
5d2b3fa
[Clang] Check explicit object param for defaulted relational operator…
MitalAshok e4bf466
Multiple diagnostics
MitalAshok e834fa5
Add tests for defaulted operator=
MitalAshok f5eceb8
Fix handling for `this A&` param missing const in defaulted relationa…
MitalAshok b9fcbea
Merge branch 'main' into explicit-obj-param-defaulted-relational
MitalAshok 1ad15e4
Merge branch 'main' into explicit-obj-param-defaulted-relational
MitalAshok f30d062
Add more tests for explicit object parameter operator==
MitalAshok 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
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
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.
I think your change loses this check - this is the
bool S::operator==(int) = default
caseThere 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.
That's checked somewhere later, this was operating on
ThisType
.For an implicit object member function,
ThisType.getNonReferenceType().getUnqualifiedType()
is alwaysContext.getRecordType(RD)
(and this shouldn't fail anyways because the diagnostic emitted here iserr_defaulted_special_member_explicit_object_mismatch
)The only difference is with explicit object member functions. The old code rejected
S& S::operator=(this int, const S&) = default;
, but acceptedS& S::operator=(this S, const S&)
since it didn't check that it was a reference.