Skip to content

Conversation

Rageking8
Copy link
Contributor

Perform some cleanup/nits and remove stray backslash (introduced in commit 79cc5de) that renders verbatim:

image

Copy link
Contributor

@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 2c56428:

✅ Validation status: passed

File Status Preview URL Details
docs/cpp/multiple-base-classes.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

@Copilot Copilot AI left a 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

@ShannonLeavitt
Copy link
Contributor

@TylerMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged Tracking label for the PR review team label Sep 26, 2025
Copy link
Contributor

Learn Build status updates of commit e397c59:

✅ Validation status: passed

File Status Preview URL Details
docs/cpp/multiple-base-classes.md ✅Succeeded

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.
Copy link
Contributor Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants