[over.oper.general] Clarify operator functions being inherited from base classes #6973
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 is not entirely clear what "inheriting" base class functions means here. It could refer to:
Judging from the context, I think it refers to the latter. This edit clarifies that by adding a reference to [class.member.lookup].
I also find "base class functions" a little bit unconventional. We probably want to say "member functions" here.