Fix accessibility description for derived interfaces - #55464
Merged
Conversation
Corrected the explanation regarding interface accessibility in derived interfaces.
Fix accessibility description for derived interfaces
BillWagner
approved these changes
Aug 18, 2026
BillWagner
left a comment
Member
There was a problem hiding this comment.
Thanks @iceland3
This LGTM, and I'll
now.
BillWagner
enabled auto-merge (squash)
August 18, 2026 14:59
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
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.
Corrected the explanation regarding interface accessibility in derived interfaces.
The original text says "cannot be narrowed," but the correct rule is "cannot be widened," as demonstrated by the code example. This change aligns the description with the actual compiler behavior.
Internal previews