[class.virtual] index semantics of final and override #4139
+2
−2
Conversation
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
Index the two paragraphs that actually specify the rules for 'final' and 'override' virt-specifiers applied to functions. I chose to index these specifiers using the 'keyword' macro rather than try to set up a separate indextext entry to ensure: 1) the index points to the right page if ever the paragraph splits across pages 2) the form is consistent with every othert index entry for these two contextual keywords, which are all created by 'keyword' Visually confirmed that the text renders in the same monospace font as the previous 'tcode' entry.
zygoloid
pushed a commit
to zygoloid/cplusplus
that referenced
this pull request
Sep 22, 2020
…plus#4139) This indexes the two paragraphs that actually specify the rules for 'final' and 'override' applied to functions.
zygoloid
pushed a commit
to zygoloid/cplusplus
that referenced
this pull request
Sep 22, 2020
…plus#4139) This indexes the two paragraphs that actually specify the rules for 'final' and 'override' applied to functions.
zygoloid
pushed a commit
that referenced
this pull request
Sep 22, 2020
This indexes the two paragraphs that actually specify the rules for 'final' and 'override' applied to functions.
tkoeppe
pushed a commit
that referenced
this pull request
Sep 22, 2020
This indexes the two paragraphs that actually specify the rules for 'final' and 'override' applied to functions.
tkoeppe
pushed a commit
that referenced
this pull request
Sep 24, 2020
This indexes the two paragraphs that actually specify the rules for 'final' and 'override' applied to functions.
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.
Index the two paragraphs that actually specify the rules for 'final'
and 'override' virt-specifiers applied to functions.
I chose to index these specifiers using the 'keyword' macro rather
than try to set up a separate indextext entry to ensure:
across pages
two contextual keywords, which are all created by 'keyword'
Visually confirmed that the text renders in the same monospace
font as the previous 'tcode' entry.