-
Notifications
You must be signed in to change notification settings - Fork 971
Remove stray backslash and some nits for "Multiple Base Classes" topic #5804
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
base: main
Are you sure you want to change the base?
Remove stray backslash and some nits for "Multiple Base Classes" topic #5804
Conversation
@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 2c56428: ✅ Validation status: passed
For more details, please refer to the build report. |
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.
Pull Request Overview
This PR cleans up the "Multiple Base Classes" documentation by fixing a rendering issue and standardizing formatting. The main purpose is to remove a stray backslash that was incorrectly rendering in the documentation and to apply consistent formatting improvements throughout the file.
Key changes:
- Remove stray backslash from pragma directive that was rendering verbatim
- Standardize image source paths and code formatting
- Update relative link paths for consistency
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Learn Build status updates of commit e397c59: ✅ Validation status: passed
For more details, please refer to the build report. |
### Dominance | ||
it's possible for more than one name (function, object, or enumerator) to be reached through an inheritance graph. Such cases are considered ambiguous with nonvirtual base classes. They're also ambiguous with virtual base classes, unless one of the names "dominates" the others. | ||
It's possible for more than one name (function, object, or enumerator) to be reached through an inheritance graph. Such cases are considered ambiguous with nonvirtual base classes. They're also ambiguous with virtual base classes, unless one of the names "dominates" the others. |
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.
Accidentally left out this nit yesterday (added in commit e397c59).
Perform some cleanup/nits and remove stray backslash (introduced in commit 79cc5de) that renders verbatim: