Fix #62738: Allow protected access with explicit 'this' parameters #62750
+606
−12
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.
Fixes #62738
The Bug
TypeScript incorrectly rejects this valid pattern:
Error:
Why this should work:
this: MyDerivedClassparameterMyDerivedClass extends MyClassthisat call sitesMaintainer confirmed: @RyanCavanaugh commented: "This specific error seems wrong"
The Fix
Modified
checkPropertyAccessibility()insrc/compiler/checker.ts:1. Check explicit
thisparameters first (for instance members only)2. Allow bidirectional type relationship when explicit
thispresentWhy This Works
When you write
function(this: DerivedClass), TypeScript already validates the type at call sites:The fix recognizes that if TypeScript already guarantees
thisis the correct type, then accessing base class protected members is safe.Test Results
TypeScript's test suites:
Before fix:
After fix:
$ tsc repro-62738.ts # Compiles successfullyWhat Still Errors (Security Maintained)
Files Changed
Modified:
src/compiler/checker.ts(40 lines)Added:
tests/cases/conformance/classes/members/accessibility/protectedAccessViaExplicitThisParameter.tsBreaking Changes
None.