[dcl.type.elab] Mix struct/class in example #2808
Merged
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
Extend the example to show that the choice of 'class' or 'struct' in an elaborated-type-name referring to a class is not significant.
|
I've seen it suggested that the sentence before the example isn't entirely unambiguous:
I think it's entirely unambiguous, but the example would reinforce the point, and seems to be in the spirit of core examples not following consistent styles of brace placement, ptr-declarator placement etc. |
|
We could also consider switching the order in that wording:
😈 |
jensmaurer
approved these changes
Apr 16, 2019
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.
Extend the example to show that the choice of
classorstructin anelaborated-type-name referring to a class is not significant.