Clarify method hiding explanation in polymorphism documentation #47378
+5
−1
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.
The polymorphism documentation's explanation of type casting with hidden base class members was confusing readers. The original text didn't clearly distinguish between method hiding (using
new
) and method overriding (usingoverride
), leading to confusion about why casting affects which method is called.Changes Made
new
keyword creates method hiding rather than overridingBefore
After
This addresses the confusion expressed in the original issue where the user asked: "if i will type cast derived class object as base class then it will call base class method, but without casting it calling to the base method then what's meaning of type casting?"
Fixes #27506.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Internal previews