[class.derived] Remove second definition of base class subobject #4058
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
jensmaurer
requested changes
Jun 25, 2020
|
Thanks. Unfortunately, the perceived definition in [intro.object] doesn't seem to be one. The mention in [class.derived] seems to be more like a definition, although there is certainly room for improvement. In short, I think the proposed change is not an improvement. |
jensmaurer
added
the
decision-required
|
Editorial meeting: We need to talk about "base class object" during name lookup, where we have no concrete object in sight. class.derived: Talk about base classes, not base class subobjects. Turn into a core issue. |
jensmaurer
added
cwg
tkoeppe
added
the
not-editorial
|
@jensmaurer Could you please create this CWG issue? |
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.
This is already defined in [intro.object].